Re: inconsistent library link

On Fri, 2004-02-06 at 21:53, Mathew Boorman wrote:
> The first time it tries to link the lib with g++, which fails.
> Building again and it links the lib with ld -shared which works fine.
> 

I think I have got more background to the linking problem.  I think some
special flags like USECXXLD are only getting set when the .o is actually
compiled, but not stored to disk.  The second time I try to build, the
compile step is not done, so it uses the normal ld.

I get a similar problem with c++ linking when a library is linked too.

The following recipe demonstrates it.  Depending on the order of the
build, 2 different link steps seem to be used.


:dll dog : dog.cpp

:program go1 
{var_LIBS= -ldog }
{var_LDFLAGS= -L. }
:
go1.cpp


Mat



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn