Re: Linking backend in one piece - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Linking backend in one piece
Date
Msg-id 200802221704.43797.peter_e@gmx.net
Whole thread Raw
In response to Re: Linking backend in one piece  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Linking backend in one piece  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: Linking backend in one piece  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Am Freitag, 22. Februar 2008 schrieb Alvaro Herrera:
> Hmm.  Do we need the text file?  I was kinda hoping we could just aggregate
> each subdir's OBJS into a big variable listing all the needed files, and
> then invoking the linker with that.

Well, my goal here was that we could use both ways of building for a while 
because we have no experience with how long command lines and argument lists 
we can handle portably.

Eventually, we could ideally transform the subdirectory Makefiles from 
independently callable Makefiles to mere include files so we have only one 
big dependency tree at the top, which would get rid of the annoying and 
time-consuming directory traversal.  This, however, raises other issues, such 
as that some compilers do not support creating output files in 
subdirectories.  I tried to support all of this in parallel but didn't 
succeeed without creating a big mess.  We can always come back to that later.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/


pgsql-hackers by date:

Previous
From: "D'Arcy J.M. Cain"
Date:
Subject: Re: Including PL/PgSQL by default
Next
From: Andrew Dunstan
Date:
Subject: Re: Including PL/PgSQL by default