Re: registry vs. environment (was re:binary
От | Claudio Natoli |
---|---|
Тема | Re: registry vs. environment (was re:binary |
Дата | |
Msg-id | A02DEC4D1073D611BAE8525405FCCE2B55F2F2@harris.memetrics.local обсуждение исходный текст |
Список | pgsql-hackers-win32 |
> 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 machine? 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 /usr/local/pgsql/lib). 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. Comments? Claudio --- Certain disclaimers and policies apply to all email sent from Memetrics. For the full text of these disclaimers and policies see <a href="http://www.memetrics.com/emailpolicy.html">http://www.memetrics.com/em ailpolicy.html</a>
В списке pgsql-hackers-win32 по дате отправления: