Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Making pgxs builds work with a relocated installation
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Magnus Hagander" <mha(at)sollentuna(dot)net>
- Cc: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: Making pgxs builds work with a relocated installation
- Date: Tue, 27 Sep 2005 13:57:11 -0400
- Message-id: <9188(dot)1127843831(at)sss(dot)pgh(dot)pa(dot)us>
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes: > Using GetShortPathName() will break on any system that has disabled > short filename generatino, which IIRC is a recommended best practice > both for performance and for security in legacy apps. I don't know what > it does, but probably it will just return the same long path again. Yuck. Anyone have another idea on coping with space-containing pathnames? I suppose we could try to quote the path variables properly in all the makefiles, but that sure seems like a painful proposition. Meanwhile, I believe I've fixed the relocatability issue per se. regards, tom lane
- Follow-Ups:
- Re: Making pgxs builds work with a relocated installation
- From: Peter Eisentraut
- Re: Making pgxs builds work with a relocated installation
- References:
- Re: Making pgxs builds work with a relocated installation
- From: Magnus Hagander
- Re: Making pgxs builds work with a relocated installation
- Prev by Date: Install pg_regress script to support PGXS?
- Next by Date: effective SELECT from child tables
- Previous by thread: Re: Making pgxs builds work with a relocated installation
- Next by thread: Re: Making pgxs builds work with a relocated installation
- Indexes: