FiveTech Software tech support forums

hi,

i wonder how to DEBUG FiveWin App which need Option "-b"
when start App i got Warning

FWDBG.DLL not found

i found c:\fwh\dll\fwdbg.dll and in this Folder also 3 x *.BAT
fwdbg64.bat, rc2dll32.bat, and rc2dll64.bat but no fwdbg32.bat

need some help please

Dear Jimmy,

Please go to FWH\samples folder and do:

buildh.bat tutor01 /b

hi Antonio,

have follow your Advice

btw. this line

Code: Select all  Expand view

%hdir%\bin\win\bcc\harbour %1 /n /i%fwh%\include;%hdir%\include /w /p %2 %3 > comp.log 2> warnings.log

must be

Code: Select all  Expand view

%hdir%\bin\harbour %1 /n /i%fwh%\include;%hdir%\include /w /p %2 %3 > comp.log 2> warnings.log

it does show Debugger but how when compile/link in other Folder where i got Warning about missing fwdbg.dll

work

Code: Select all  Expand view

  c:\fwh\samples\tutor01.prg

do not work

Code: Select all  Expand view

   c:\fwh\0\FWVLC\FWVLC.PRG

i try to include c:\fwh\dll into PATH but still got Warning ... have to copy fwdbg.dll into App Folder to work

Dear Jimmy,

Up to recently we used the same folders configuration as Clipper: bin, lib, include folders.

But as we can build in 32 or 64 bits, using Borland, Microsoft or MinGW, we have decided to respect the same directory structure as Harbour uses:

harbour/bin/win/bcc
harbour/bin/win/msvc
harbour/bin/win/msvc64
harbour/bin/win/mingw
etc...

from FWH 22.06 on we are using this folders structure, so you can easily build using 32 or 64 bits, or using any of those compilers. That would be impossible
using harbour/bin only. The same structure applies for the lib folder.

hi Antonio,

i´m not sure about your last Answer which seems have to do with harbour/Bin ...
> bin, lib, include folders.

my "Problem" is c:\fwh\dll\fwdbg.dll which is "unknown" when not using c:\fwh\samples\

---

i have create Sub-Folder under C:\fwh for my own Project

Code: Select all  Expand view

c:\fwh\0\VLC\

now i have to "copy" fwdbg.dll into Folder to make it work

i have try to include c:\fwh\dll into PATH but still got Warning "not found"

Question : is there any "SET FWDEBUG ="

Dear Jimmy,

You have to copy fwdbg.dll where your EXE is placed

hi Antonio,

Antonio Linares wrote:You have to copy fwdbg.dll where your EXE is placed

Ok, got it
Thx

Jimmy

Debug is a very handy tool to have .. you can debug also and trap values at runtime with Msginfo() .. you can easily evaluate memory variables, module tracing, etc ....

Rick Lipkin

There is wonderful debugger on VSCode

Dear Antonino,

+1

Hello AntoninoP,

is there some info how to start using VSCode debugger?

Best regards,
Otto

Otto wrote:Hello AntoninoP,

is there some info how to start using VSCode debugger?

Best regards,
Otto

I always suggest the very good guide by Eric Lendvai https://harbour.wiki/index.asp?page=PublicArticles&mode=show&id=190401174818&sig=6893630672

Hello Antonino,
Thank you. I will try.

Best regards,
Otto