On Thu, 01 Oct 2009, Szak�ts Viktor wrote: Hi Viktor,
>> Binary file import32.lib matches >> Binary file intraweb_100_140.lib matches >> Binary file ws2_32.lib matches >> How can I include these libs to build Harbour? > Thanks. ws2_32 is already on the liblist, so the problem > may lie elsewhere As I can see ws2_32 is not given when harbour.dll is linked. We have: ilink32.exe -q -Gn -C -aa -Tpd -Gi -x c0d32.obj @__dyn__.tmp and inside __dyn__.tmp: ..\..\..\..\..\source\common\obj\win\bcc\expropt1_dyn.obj + [...] ..\..\..\..\..\source\vm\obj\win\bcc\vm_dyn.obj + , ..\..\..\..\..\bin\win\bcc\harbour-20-bcc.dll,, cw32mt.lib import32.lib so only w32mt.lib and import32.lib which are hrdcoded in win/bcc.mk are passed and it could be the source of problem. For me it looks like a typo and instead of DLIBS := $(foreach lib,$(LIBS),$(LIB_DIR)/$(lib)$(LIB_EXT)) we should have DLIBS := $(foreach lib,$(LIBS) $(SYSLIBS),$(lib)$(LIB_EXT)) best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
