Horton

Re: Postgres Windows build system doesn't work with python installed in Program Files

Ranier Vilela <ranier.vf@gmail.com>

View thread View on postgr.es
From: Ranier Vilela <ranier.vf@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Victor Wagner <vitus@wagner.pp.ru>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-05-06T13:25:41Z
Lists: pgsql-hackers 
Em qua., 6 de mai. de 2020 às 10:21, Ranier Vilela <ranier.vf@gmail.com>
escreveu:

> Em qua., 6 de mai. de 2020 às 09:53, Michael Paquier <michael@paquier.xyz>
> escreveu:
>
>> On Tue, May 05, 2020 at 10:16:23AM +0300, Victor Wagner wrote:
>> > I agree, it is better.
>>
>> Thanks, applied and back-patched down to 9.5.  Now for the second
>> problem of this thread..
>>
> Sorry, no clue yet.
> I hacked the perl sources, to hardcoded perl, bison and flex with path.It
> works like this.
> For some reason, which I haven't yet discovered, msbuild is ignoring the
> path, where perl and bison and flex are.
> Although it is being set, within the 64-bit compilation environment of
> msvc 2019.
> I'm still investigating.
>
In fact perl, it is found, otherwise, neither build.pl would be working.
But within the perl environment, when the system call is made, in this
case, neither perl, bison, nor flex is found.

regards,
Ranier Vilela

Commits

  1. Improve perl script in MSVC to build binaries

  2. Handle spaces for Python install location in MSVC scripts

  3. Use perl's $/ more idiomatically