From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: A quick warning on the win32 build scripts |
Date: | 2010-12-20 16:56:34 |
Message-ID: | AANLkTin3u9arocr14CA8nJtt+jcaWvTOPGj7Qsg9+zib@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
(Hello, very old thread)
On Tue, Oct 5, 2010 at 16:29, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
>> The cause turns out to be the automatic .DEF file generation. It skips
>> DEF file generation if a DEF file already exists, even if the
>> object/sources are newer than the existing DEF file.
>
> Um, so can't we fix that? It seems like a rather basic expectation of a
> build process that it will rebuild dependent files when needed.
Does anybody have an idea of *how* to actually do that?
My first thought was to just generate a DEF file whenever any of the
object files have changed, which could be a simple date comparison.
However, generating the DEF file is *really* expensive and slow, so
this would make rebuilding anything that *doesn't* add or remove an
entrypoint unacceptably slow..
Can someone think of a way to do this without having to dump the list
of exports from each and every object file?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-12-20 17:00:03 | Re: unlogged tables |
Previous Message | Robert Haas | 2010-12-20 16:54:19 | Re: serializable lock consistency |