> >> Why not? The shipped tarball would contain exactly the same
> >> pg_config.h.win32 it does today; the only difference is that the
> >> version info would've been inserted automatically instead of
> >> manually.
>
> > Right. And then you can only build from tarball and not
> from CVS, righ
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> Why not? The shipped tarball would contain exactly the same
>> pg_config.h.win32 it does today; the only difference is that
>> the version info would've been inserted automatically instead
>> of manually.
> Right. And then you can only build from
> >> Sorry - we're just talking about getting the version
> number in there
> >> automatically to avoid it getting forgotten during release
> bundling.
>
> > I can see that being a good idea. But I don't see Toms ./configure
> > solution working.
>
> Why not? The shipped tarball would contai
Tom Lane wrote:
> Why not? The shipped tarball would contain exactly the same
> pg_config.h.win32 it does today; the only difference is that the
> version info would've been inserted automatically instead of
> manually.
I suggest you do it in a makefile as part of the distprep target.
distprep:
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> Sorry - we're just talking about getting the version number
>> in there automatically to avoid it getting forgotten during
>> release bundling.
> I can see that being a good idea. But I don't see Toms ./configure
> solution working.
Why not? The
> > Getting late into this discussion, so I may be completely
> off here :-)
> > How's that going to work+ pg_config.h.win32 needs to know
> > win32 platform
> > specifics, right? So it has to be created, in that case, on
> win32. But
> > when you're building with MSVC, you don't run configure,
> -Original Message-
> From: Magnus Hagander [mailto:[EMAIL PROTECTED]
> Sent: 24 October 2006 15:56
> To: Tom Lane; Dave Page
> Cc: pgsql-hackers@postgresql.org
> Subject: RE: [HACKERS] Release stamping (Was: [CORE] Schedule
> for release?)
>
> Getting la
> >> The pg_config.h.win32 file is intended to support building in an
> >> environment where you can't run automake/autoconf, or
> indeed much of
> >> anything else.
>
> > That doesn't matter does it? Marc runs the bootstrap, which inserts
> > the version numbers into the right place and runs
Tom Lane wrote:
> Hmm, so manufacture pg_config.h.win32 during tarball build and insert
> the version numbers at that point? Yeah, that would work. Actually
> the easiest thing would likely be to have configure build it the same
> way it builds pg_config.h, and then not remove it in "make
> distc
"Dave Page" writes:
> From: Tom Lane [mailto:[EMAIL PROTECTED]
>> The pg_config.h.win32 file is intended to support building in an
>> environment where you can't run automake/autoconf, or indeed much of
>> anything else.
> That doesn't matter does it? Marc runs the bootstrap, which inserts the
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 24 October 2006 14:30
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [CORE] Schedule for release?
>
> > In pgAdmin we have a simple bootstrap script the writes all
> the version
> > numbers into a bunch o
11 matches
Mail list logo
