Skip site navigation (1) Skip section navigation (2)

Re: Release stamping (Was: [CORE] Schedule for release?)

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Release stamping (Was: [CORE] Schedule for release?)
Date: 2006-10-24 15:02:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> > 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, because 
> > windows can't run that (without the mingw layer).
> 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.

What we could do is have the msvc build scripts edit the file and
replace the version with something it reads from when run.
This would require that we zap the old "win32.mak" method of buildnig
win32 stuff, which we can't do just yet but IMHO can eventually do. 

The other option is, I would think, to break out the version #defines
into a separate headerfile that's used on all platforms, and use that
one *instead* of configure to set it.


In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2006-10-24 15:16:40
Subject: Re: Release stamping (Was: [CORE] Schedule for release?)
Previous:From: Dave PageDate: 2006-10-24 14:59:25
Subject: Re: Release stamping (Was: [CORE] Schedule for release?)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group