AW: problems with make...
Tony Wetmore
tony.wetmore@solipsys.com
Wed Feb 9 15:10:00 GMT 2005
Jupp: This is definitely a question to be answered by a Qt mailing
list. It has nothing to do with gcc. Even make is not a part of gcc,
so that likely has its own mailing list as well.
Corey: If you are linking an executable against a static library, as
Jupp is doing, you must re-link the executable if the library changes,
otherwise your executable will NOT see the changes made in the library.
This is definitely something you would do in a Makefile for your
executable, probably something like this:
executable: main.o staticlibrary.a
LINK_COMMAND_HERE
That rule would trigger a re-link of the executable if either main.o or
staticlibrary.a were changed.
---
Tony Wetmore
Raytheon Solipsys
mailto:tony.wetmore@solipsys.com
http://www.solipsys.com
-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of corey taylor
Sent: Tuesday, February 08, 2005 5:11 PM
To: Jupp Tscheak
Cc: gcc-help@gcc.gnu.org
Subject: Re: AW: problems with make...
Well, I don't exactly see why you would want that.
However, that's an automake, make issue. I'm not sure if you can
specify a binary in the dependency list though.
Corey
On Tue, 8 Feb 2005 22:54:42 +0100, Jupp Tscheak <jupp_tscheak@gmx.de>
wrote:
> Hi corey,
>
> if a static linked library has changed the whole binary should be
> recomplied. If make notices that any of the sources are newer than the
> binary it recompiles. This behaviour should be the same if the static
> lib is newer than the binary. That isn't the case. Can you explain
> this?
>
> Jupp
>
> -----Ursprüngliche Nachricht-----
> Von: corey taylor [mailto:corey.taylor@gmail.com]
> Gesendet: Dienstag, 8. Februar 2005 22:44
> An: Jupp Tscheak
> Cc: gcc-help@gcc.gnu.org
> Betreff: Re: problems with make...
>
> Jupp,
>
> For what behavior are you looking?
>
> corey
>
> On Tue, 8 Feb 2005 22:40:45 +0100, Jupp Tscheak <jupp_tscheak@gmx.de>
> wrote:
> > Hi,
> >
> > we're building our project with automatic generated Makefiles (using
> > qt's .pro files, although some modules have nothing to do with qt!).
> > The problem is that if a static linked library has changed, it says
> > "nothing to be done for..." (binary file is older than static lib so
> > it should be relinked). Does anyone know how to avoid this behavior
> > (any flags for g++)?
> >
> > Thanks in advance
> >
> > Jupp Tscheak
> >
> >
>
>
More information about the Gcc-help
mailing list