Re: build environment: a different makefile

From: "Dave Page" <dpage(at)postgresql(dot)org>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "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 08:09:24
Message-ID: 937d27e10802070009i4c2c7472l5d498b60d06bc363@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

/D

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2008-02-07 08:15:33 Re: Page-at-a-time Locking Considerations
Previous Message James Mansion 2008-02-07 07:15:39 Re: PostgreSQL 8.4 development plan