Hi Przemek,
Very good point. It may explain Toninho's problem
well. Since he was not using the central config files
(which is BTW an install time requirement for all
Borland C compilers), and he was only copying in
bcc32.cfg, ilink32 was clueless about lib dirs.
Thanks a lot. This also means this is a local
env problem, not a Harbour one.
I'd recommend everyone to follow official steps
to setup C tools (for MSVC it's vsvars*.bat or
something alike). Maybe we should have a document
on this.
Brgds,
Viktor
On 2008.11.12., at 20:19, Przemyslaw Czerpak wrote:
On Wed, 12 Nov 2008, Szak�ts Viktor wrote:
Hi Viktor and Toninho
BTW, do you have a 'c0d32.obj' in your Borland lib dir?
Yes, I have.
Very strange. No more ideas here. Anyone?
Please check the location of c0d32.obj and if it's known for BCC
compiler so it can locate during linking. AFAIR ilink in BCC needs
valid paths set in ilink32.cfg. It was -L option or sth like that.
You can also use bcc32.exe as wrapper to ilink32.exe and if I'm
not wrong in such case link switches in bcc32.cfg are passed to
ilink32.exe.
best regards,
Przemek
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour