when I compile with xharbour.com and FWH 16.02 I got error
Type: C >>>xlink.exe -NOEXPOBJ -MAP -FORCE:MULTIPLE -NOIMPLIB -subsystem:windows -UNMANGLE -LIBPATH:"S:\lib" -LIBPATH:"R:\lib" -LIBPATH:"R:\c_lib" -LIBPATH:"R:\c_lib\win" "t.obj" "S:\lib\send32.lib" "S:\lib\mem32.lib" "S:\lib\png.lib" "r:\c_lib\win\gdi32.lib" "r:\c_lib\win\gdiplus.lib" "xhbzip.lib" "xhbzipdll.lib" "R:\c_lib\win\psapi.lib" "xfw.lib" "FiveHCM.lib" "FiveHMX.lib" "OptG.lib" "xhb.lib" "dbf.lib" "nsx.lib" "ntx.lib" "cdx.lib" "rmdbfcdx.lib" "ct3comm.lib" crt.lib kernel32.lib user32.lib winspool.lib ole32.lib oleaut32.lib odbc32.lib odbccp32.lib uuid.lib wsock32.lib ws2_32.lib wininet.lib advapi32.lib shlwapi.lib msimg32.lib mpr.lib OleDlg.lib version.lib comctl32.lib comdlg32.lib gdi32.lib shell32.lib winmm.lib lz32.lib Netapi32.lib -out:"t.exe"<<<
Creating object: t.EXP
Creating library: t.LIB
xLINK: error: Unresolved external symbol '_HB_FUN_WNDREADPALBMPEX referenced from Fivehmx.lib(window.obj)'.
xLINK: error: Unresolved external symbol '_HB_FUN_WNDSAYTEXT referenced from Fivehmx.lib(window.obj)'.
xLINK: error: Unresolved external symbol '_HB_FUN_WNDSAYPALBMP referenced from Fivehmx.lib(window.obj)'.
xLINK: error: Unresolved external symbol '_HB_FUN_FW_DRAWSHAPES referenced from Fivehmx.lib(window.obj)'.
xLINK: error: Unresolved external symbol '_HB_FUN_CALCTEXTWH referenced from Fivehmx.lib(buttonb.obj)'.
xLINK: error: Unresolved external symbol '_HB_FUN_ISXHBCOM referenced from Fivehmx.lib(xbrowse.obj)'.
xLINK: error: Unresolved external symbol '_HB_FUN_MEMORYBUFFERTYPE referenced from Fivehmx.lib(xbrowse.obj)'.
xLINK: error: Unresolved external symbol '_HB_FUN_FW_CREATEBITMAP referenced from Fivehmx.lib(xbrowse.obj)'.
xLINK: fatal error: 8 unresolved external(s).
Type: C >>>Couldn't build: t.exe<<<
Type: C >>>TMAKEPROJECT<<<
Type: C >>>TMAKEPROJECT:REFRESH<<<
Type: N >>> 1406<<<
best regards
kajot
problem with FW 16.02
- Antonio Linares
- Site Admin
- Posts: 42512
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Has thanked: 31 times
- Been thanked: 73 times
- Contact:
Re: problem with FW 16.02
Kajot,
I have just emailed you modified FWH 16.02 libraries for xhb.com
Please try with the new ones, thanks
sorry for these inconveniencies
I have just emailed you modified FWH 16.02 libraries for xhb.com
Please try with the new ones, thanks
sorry for these inconveniencies
- TimStone
- Posts: 2954
- Joined: Fri Oct 07, 2005 1:45 pm
- Location: Trabuco Canyon, CA USA
- Has thanked: 25 times
- Been thanked: 2 times
- Contact:
Re: problem with FW 16.02
Antonio,
I just checked. I have two major apps that are also built with .xhb ( com ) and they both had no problems building with the first release of 16.02.
When you did a new build of .libs, what was missing ? Apparently I picked it up in some other file.
Tim
I just checked. I have two major apps that are also built with .xhb ( com ) and they both had no problems building with the first release of 16.02.
When you did a new build of .libs, what was missing ? Apparently I picked it up in some other file.
Tim
Tim Stone
http://www.MasterLinkSoftware.com
http://www.autoshopwriter.com
timstone@masterlinksoftware.com
Using: FWH 23.10 with Harbour 3.2.0 / Microsoft Visual Studio Community 2022-24 32/64 bit
http://www.MasterLinkSoftware.com
http://www.autoshopwriter.com
timstone@masterlinksoftware.com
Using: FWH 23.10 with Harbour 3.2.0 / Microsoft Visual Studio Community 2022-24 32/64 bit
- Antonio Linares
- Site Admin
- Posts: 42512
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Has thanked: 31 times
- Been thanked: 73 times
- Contact:
Re: problem with FW 16.02
Tim,
There was a PRG that somehow was not compiled and placed into the lib for xhb.com.
If you are able to create the EXEs then your libs are fine.
There was a PRG that somehow was not compiled and placed into the lib for xhb.com.
If you are able to create the EXEs then your libs are fine.