Re: [NOVICE] Python verison for build in config.pl (Win32)
От | Magnus Hagander |
---|---|
Тема | Re: [NOVICE] Python verison for build in config.pl (Win32) |
Дата | |
Msg-id | 9837222c1001201109j245a8b2cl12651e104634a7a1@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [NOVICE] Python verison for build in config.pl (Win32) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [NOVICE] Python verison for build in config.pl (Win32)
|
Список | pgsql-hackers |
On Wed, Jan 20, 2010 at 18:59, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Matt <bsg075@gmail.com> writes: >> Attempting to build 8.5 alpha on Windows XP (MSVC 2005) with Python support. >> Path to local interpreter added to config.pl (C:\Python), but message is >> presented: > >> "Could not determine python version from path at build.pl line 38" > >> Do the build scripts attempt to determine the Python version from the path >> name? Since my machine has a generic path name, is there a way to specify >> the interpreter version? > > Hm, I see this in Mkvcbuild.pm: > > $solution->{options}->{python} =~ /\\Python(\d{2})/i > || croak "Could not determine python version from path"; > $plpython->AddLibrary($solution->{options}->{python} . "\\Libs\\python$1.lib"); > > Apparently you need to hack that to deduce the appropriate library > pathname. What exactly is your python path name, and is it a standard > installation pattern at all? From the OP, it's c:\python. And yes, the python version detection is very naive, in that it expects the default installation paths which are c:\python25 for example. So you'll need to move your python installation to the default location. Or we'd welcome a patch for a smarter way to detect the version ;) -- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
В списке pgsql-hackers по дате отправления: