search

mapbox / windows-builds

DEPRECATED! build scripts for mapnik dependencies, mapnik, node-mapnik, node, libosmiom, osmium-tool
38 stars 22 forks source link

python not on PATH for node-mapnik build #8

Closed springmeyer closed 9 years ago

springmeyer commented 9 years ago

ran into this - perhaps python should be put on PATH via settings.bat?

wilhelmberg commented 9 years ago

It's already in settings.bat. Maybe you have it installed to the different directory?

The different Python versions for boost (x86/x64) are being set here.

springmeyer commented 9 years ago

I did have a globally installed python around that was causing issues. After deleting it then no python was on my path even after running settings. I will take a closer look next time I boot the ec2 machine I'm testing with. Thanks!

wilhelmberg commented 9 years ago

Python doesn't get installed, it just gets extracted. That's why after running settings you don't get it on the commandline.

When we were working on boost, we agreed that we have a system wide 32bit Python install (for gyp) and the local extracts for boost.

e.g. build.bat calls build_python.bat and build_boost.bat uses it like this.

springmeyer commented 9 years ago

When we were working on boost, we agreed that we have a system wide 32bit Python install (for gyp) and the local extracts for boost.

Hmm, don't recall the logic here. What about just always using/expecting our local extracts of python?

springmeyer commented 9 years ago

just bull nosing this trying to get things working, This fix worked for the 64 bit build of build_node_mapnik.bat (https://github.com/BergWerkGIS/mapnik-dependencies/commit/bebca605e2a8f10b9ba764a140aeb45b7152ff4e), but when running build_mapnik.bat on the 32 bit build I'm seeing: screen shot 2014-10-02 at 6 17 16 pm

springmeyer commented 9 years ago

looks like for the 64 bit install python27.dll ends up in the main directory but it is not there for the 32 bit install (not in the python-2-x86-32 folder)

wilhelmberg commented 9 years ago

Hmm, don't recall the logic here. What about just always using/expecting our local extracts of python?

We had problems with gyp and 64 bit python.

but when running build_mapnik.bat on the 32 bit build I'm seeing

Did you do scripts\build_python.bat before scripts\build_mapnik.bat?

I had concurrency problems with python on a completely new install from within mapnik-gyp when pip gets installed. From the second run on everthing seems fine.

BTW: just completed 32bit and 64 builds without problems. With gdal 1.11.0, will try with gdal 1.11.1 next.

springmeyer commented 9 years ago

BTW: just completed 32bit and 64 builds without problems.

Fantastic. Looks like my problems may be due to the 64 Bit mapnik-deps\tmp-bin being on my global PATH: https://github.com/BergWerkGIS/mapnik-dependencies/issues/10#issuecomment-57840739