Re: build environment: a different makefile

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Dave Page <dpage(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Paul van den Bogaard <Paul(dot)Vandenbogaard(at)sun(dot)com>
Subject: Re: build environment: a different makefile
Date: 2008-02-07 09:21:52
Message-ID: 20080207092152.GC12085@svr2.hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 07, 2008 at 08:09:24AM +0000, Dave Page wrote:
> On Feb 6, 2008 11:12 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> > I've sometimes wondered whether the SUBSYS.o files really offer any
> > advantage compared to just linking all the individual .o files. They
> > certainly eat disk space, but perhaps they save some time ... or perhaps
> > not, especially in a one-off build.
>
> Getting rid of them would certainly make building OSX universal binaries easier.
>
> > I suppose that we might fall foul of command line length limits on
> > some platforms :-(. The output of your find command amounts to nearly
> > 11000 characters in HEAD.
>
> What do other large build systems do?

FWIW, the MSVC build ends up writing the list of object files to a temp
file and then having the linker read that list. (This is all done behind
the scenes though, it's not something we made up) IIRC the gcc linker can
also take the commandline from a file instead of the actual commandline,
which should be workable I think.

//Magnus

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zdenek Kotala 2008-02-07 09:28:57 Re: Page-at-a-time Locking Considerations
Previous Message Simon Riggs 2008-02-07 08:53:32 Re: Page-at-a-time Locking Considerations