>Hi Viktor and Toninho

>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.

Hi Przemek and Viktor,

I found the problem.

With latest changes in makefiles now we need:

---bcc32.cfg---
-IE:\harbour\bcc55\include;E:\harbour\bcc55\include\dinkumware
-LE:\harbour\bcc55\lib
---bcc32.cfg---

*** AND***

---ilink32.cfg---
-LE:\harbour\bcc55\lib"
---ilink32.cfg---


Now Harbour compiles fine.

Thanks and best regards,

Toninho.

__________________________________________________
Faça ligações para outros computadores com o novo Yahoo! Messenger
http://br.beta.messenger.yahoo.com/
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to