Re: win32 version info

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: <mha(at)sollentuna(dot)net>
Cc: <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <andrew(at)dunslane(dot)net>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: win32 version info
Date: 2004-07-29 12:29:51
Message-ID: 4441.24.211.141.25.1091104191.squirrel@www.dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Magnus Hagander said:

>
> One more thing I realised - we need two different types of versioninfo
> structures, because one fields tells wether it's a DLL or an app. How
> would you prefer this done - either using $(WIN32VERDLL)/$(WIN32VERAPP)
> (or $(PORTOBJSHLIB)/$(PORTOBJAPP) if we go down that route), or by
> setting another field along FILEDESC called FILETYPE or similar?
>

I think I would go with PORTOBJ + FILEDESC + FILETYPE for now. ISTM that
gets it clean enough, and it can be revisited later if necessary.

One thing that I think Peter referred to - libraries that we version (e.g.
libpq) in standard Unix major.minor style should probably carry that version
rather than the PostgreSQL version number.

cheers

andrew

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Magnus Hagander 2004-07-29 12:46:43 Re: win32 version info
Previous Message Andreas Pflug 2004-07-29 11:31:53 Re: Admin functions contrib