buildhd.bat babudll is generating errors in FWH 2.8 Sept.

RAMESHBABU · Post by **RAMESHBABU** » Tue Oct 03, 2006 8:36 pm

Hello Mr.Antonio

When I tried to build BABUDLL.DLL with BUILDHD BABUDLL,
I am getting the following error:

Error: Unresolved external '_hb_vmProcessSymbolxEx'Referenced from C:\FWH\LIB\FIVEHX.LIB|ALERT

Please guide me what to do.

Regards,

- Ramesh Babu P

Post by **Antonio Linares** » Tue Oct 03, 2006 9:55 pm

Ramesh,

Please use this harbour build:
http://hyperupload.com/download/02817d0 ... r.zip.html

RAMESHBABU · Post by **RAMESHBABU** » Wed Oct 04, 2006 2:07 am

Hello Mr.Antonio

Now after installing harbour form the download, I could build the
BABUDLL.DLL without errors.

Now when I try to check it with BABU.EXE the code from the DLL is
not working and only "ok from EXE" which is from the exe itself is
displayed using xHarbour.

When I tried to check it with HARBOUR.EXE I am getting the follwing
message

Error: Unresolved external '_hb_fun__CLSCNTCLASSES' referenced from C:\FWH\LIB\FIVEHX.LIB|errsysw

I am not clear here:

a) Can't we build Self contained DLLs from XHARBOUR ? (The buildhd.bat
is calling harbour.exe from HARBOUR directory from FWH\SAMPLES
folder)

b) If we can't build them from XHARBOUR, all our functions/procedures
meant for storing in DLL are to be re-written in HARBOUR ? (all third
party libs meant for xHARBOUR, may not work with HARBOUR).

Any solution?

Regards to you,

- Ramesh Babu P

Post by **Antonio Linares** » Wed Oct 04, 2006 6:18 am

Ramesh,

samples\babu.prg and babudll.prg were properly working with previous Harbour builds. It looks as something has changed into Harbour and now the DLL is no longer working. This is an issue that has to be checked with the Harbour developers list.

>
a) Can't we build Self contained DLLs from XHARBOUR ? (The buildhd.bat
is calling harbour.exe from HARBOUR directory from FWH\SAMPLES
folder)
>

xharbour should be compatible with Harbour on this issue.

>
b) If we can't build them from XHARBOUR, all our functions/procedures
meant for storing in DLL are to be re-written in HARBOUR ? (all third
party libs meant for xHARBOUR, may not work with HARBOUR).
>

If the DLL is a self contained one and does not use the EXE virtual machine, then you could have you EXE built in any language.

Anyhow, these are Harbour/xHarbour issues, not FWH ones.

Post by **Antonio Linares** » Wed Oct 04, 2006 6:49 am

Ramesh,

Use this Harbour build:
http://hyperupload.com/download/02817d0 ... r.zip.html

And both samples\babu.prg and babudll.prg work fine.

RAMESHBABU · Post by **RAMESHBABU** » Wed Oct 04, 2006 1:38 pm

Hello Mr.Antonio

Thank you very much for your answers and revised harbour.exe

I know these are Harbour issues.

Where should we go!. We will first bother you only because you are our master.

Regards to you,

- Ramesh Babu P