> The remaining issue I see which is somewhat related to this
> is: how do we allow an installation path to be set at install time
> rather than at configure time (in the usual Windows way)? And how do we do
> that and at the same time provide for multiple installations on the same
Good question. The problem as I see it is being able to resolve things like
PKGLIBDIR/$libdir (which, at configure time, gets set to something like
If we restrict the Win32 port to prevent the use of configure time --libdir,
--bindir etc (ie. we force the PostgreSQL lib, bin, share, include
directories to fall under the same root directory, as is the default [ie.
/usr/local/pgsql]), then one obvious solution would be to resolve, say
$libdir, under Win32 by taking the basename of progname and appending
../lib. Doesn't seem like a totally unreasonable approach for this platform.
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see
pgsql-hackers-win32 by date
|Next:||From: Florian Weimer||Date: 2004-02-15 13:05:16|
|Subject: Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint|
|Previous:||From: Merlin Moncure||Date: 2004-02-13 19:33:18|
|Subject: Re: Problem with win 32 libpq calls|