FiveTech Software tech support forums

Tim,

If your FWH (February) application properly links with the xharbour that you have, then you have the right one. If not, you will get some missing external symbols.

xharbour introduced these changes before Harbour, so xHB February should be ok with FWH February build.

I wanted to build the sample testrtf.prg with xHarbour ( Feb ) and FWH 2.7. I receive the following undefined external symbols: _GetFileVersionInfoSizeA _GetFileVersionInfoA _VerQueryValueA I am simply trying to build the sample included with 2.7. What am I missing here ? Thanks. ...

I wanted to build the sample testrtf.prg with xHarbour ( Feb ) and FWH 2.7.

I receive the following undefined external symbols:

_GetFileVersionInfoSizeA
_GetFileVersionInfoA
_VerQueryValueA

I am simply trying to build the sample included with 2.7.

What am I missing here ?

Thanks.

Tim

... of the OBJs (static) symbol table) used by that pcode: (please review hbpcode.h for the currently implemented pcode opcodes) VM( pcode, local symbols ) The VM may invoke the VM (itself) again. This lets the Clipper language access Clipper functions and methods and external C language functions ...

If I link in Ct3.Lib with FWH 2.7 (MSVC / xHarbour), I get unresolved symbols in _hb_stack (e.g. CharOne).