Hi Vailton, > Turbo Incremental Link 5.00 Copyright (c) 1997, 2000 Borland
Fatal: Unable to open file 'NDDEAPI.LIB' hbmk: Error: Running linker. 2: ilink32.exe @C:\Users\VAILTO~1\AppData\Local\Temp\u9m8j1.lnk This is caused by incomplete bcc32.cfg/ilink32.cfg, also see my prev mail. It's not hbmk2 or Harbour hbp job to fix incomplete bcc installations, so it should be corrected locally. Unfortunate Borland forgot to highlight this configuration detail in their README. Anyway you can also add the PSDK lib manually on the command line or additional local .hbp file, but I'd prefer to leave it for now from our files since they'd be highly bcc specific hacks on the wrong place. Besides, we would have to know the location of PSDK dir on users computer, which cannot be done without further ugly hacks and knowledge of version specific / non-documented bcc internals. C:\Users\VAILTO~1\AppData\Local\Temp\hbmk_tg6vjx.c: > Turbo Incremental Link 5.00 Copyright (c) 1997, 2000 Borland > Error: Unresolved external 'AlphaBlend' referenced from > F:\FW\FWH_9.04\LIB\FIVEH > C.LIB|BRUSHES > hbmk: Error: Running linker. 2: > ilink32.exe @C:\Users\VAILTO~1\AppData\Local\Temp\cz3x7z.lnk I've found that bcc codepath didn't add hbmk2 win sys liblist to the linker command. I'll correct that ASAP. At the same time this will mean that hbmk2 will be broken for everyone with not properly configured bcc. In some other cases, the FW provides native support for ODBC and ODBC32.LIB is missing inside fwh.hbp... See it in buildh.bat which is > posted above. I'll add odbc32 lib to the std list of system headers. If anyone is aware of any problems this may cause, pls tell. Alternatively we can add it to fwh.hbp. Brgds, Viktor
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
