fixes to src and binding.byp to allow windows installation

[adube]

I was able to manually build node-mapserv on a Windows 7 64 bits machine with the following fixes.

The binding.gyp requires 2 variables to be manually set before configuring:

"variables": {
    'ms_buildkit%': 'Z:/PATH/TO/MAPSERVER_BUILDKIT',
    'ms_root%': 'Z:/PATH/TO/MAPSERVER'
},

[homme]

Hi Alexandre,

That's great to hear you got it working and thanks for the code. I'm looking to repeat your steps and then parameterise the package using the tools/config.py script so that the build ties in better with npm (e.g. I think we can probably get all the libraries using the script rather than listing them manually). It looks like the ms_buildkit comes from the compiled libraries and headers file (e.g. release-1600-x64-gdal-1-10-0-mapserver-6-2-1-libs.zip from this page) but which is the ms_root package that includes the mapserver_i.lib referenced in binding.gyp?

[juliensam]

Hello,

I worked with Alexandre on this issue. We used our own version of MapServer for this. When compiling we need a working mapserver_i.lib which is not included in the release package you pointed. It's fairly easy to do it yourself.

• Download the SDK from the GDAL and MapServer build SDK packages section here
• Download the MapServer source
• Put the source at the root of the SDK
• Adapt the Makefile to point to your mapserver directory (Search for MS_DIR)
• In a MSVS console go in the sdk directory and type: nmake ms

To test yourself, you can download our pre-compiled buildkit here (VS2010 and 32bit): http://dl.mapgears.com/ab-tmp/mapserver-buildkit-vs2010.zip

[homme]

@juliensam Thanks very much! Hopefully that will help anyone else going down the same route.

[adube]

@homme Thanks for the review and merge.

[homme]

@adube A pleasure - thanks for the contribution and I hope my comments in WINDOWS-INSTALL.md are along the right lines.