Closed springmeyer closed 8 years ago
Till the next release is out, a temporary workaround for Mapbox Studio 0.2.7 64bit is to:
vcredist_x64-mini.7z
to a temporary folder, e.g.: C:\MBSDLLs
(can be deleted afterwards)C:\MBSDLLs
intoC:\Program Files\mapbox-studio\resources\app\vendor
C:\MBSDLLs
intoC:\Program Files\mapbox-studio\resources\app\node_modules\mapnik\lib\binding\node-v11-win32-x64
@BergWerkGIS That workaround worked like a charm for me - thanks for updating the issue.
@slibby Perfect! Thanks for lettings us know, that this worked for you.
Thanks for this quick'n'dirty but useful workaround, @BergWerkGIS ! Hope to see new release very soon.
In the meantime I created a very simple installation package as my NSIS homework for even easier application of your solution. The libraries archive is available as a self-extracting binary by this NSIS script thanks to the Crazy Tronners. :)
noting that https://github.com/mapbox/mapbox-studio/compare/vs2015 is the branch that @BergWerkGIS has been working on that will solve this and with the latest commit we've moved to node v0.10.40 and all tests are passing on travis and windows /cc @GretaCB @flippmoke
For workaround with current 0.2.7 see above.
Next release will include needed files.
The current release of Mapbox Studio v0.2.7 includes libraries internally that depend on Visual Studio 2014 CTP 4. This is fine is most cases. The libraries are installed on the system when the Mapbox Studio installer runs. And then Mapbox studio can use them and benefit from high performance rendering features that leverage the C++11 Standard (only available in pre-release Visual Studio versions).
However Microsoft has:
Both of these installations conflict with the 2014 CTP libraries Microsoft previously released. This is not fun, but expected. So, if anyone installs Visual Studio 2015 then Mapbox Studio will no longer open.
@BergWerkGIS and I have been working hard to anticipate this breakage and prepare the foundations for a new Mapbox Studio release that will work seamlessly with both:
So, the upcoming Mapbox Studio v0.2.8 will fix this. For users who have a broken install of Mapbox Studio currently please share the details below of what Visual Studio version you have installed and we'll try to help you troubleshoot.