Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question on mapbox-node-binary.s3.amazonaws.com/mapnik #891

Closed
pausto opened this issue Jul 11, 2018 · 2 comments
Closed

Question on mapbox-node-binary.s3.amazonaws.com/mapnik #891

pausto opened this issue Jul 11, 2018 · 2 comments

Comments

@pausto
Copy link

pausto commented Jul 11, 2018

Is it possible to lay out the index of the contents of this folder to understand for which version there are compiled files, for example,
https://mapbox-node-binary.s3.amazonaws.com/mapnik/v3.5.2/Release/node-v48-win32-x64.tar.gz
https://mapbox-node-binary.s3.amazonaws.com/mapnik/v3.6.2/Release/node-v48-win32-x64.tar.gz
Where can I see what files are on this server? And knowing them, put the right version of mapnik

@Algunenano
Copy link
Contributor

Windows prebuilt binaries are no longer supported (#848) but compilation should still work.

The last published binaries were for 3.6.2 but I see they were uploaded with a different format (https://mapbox-node-binary.s3.amazonaws.com/mapnik/v3.6.2/node-v48-win32-x64-Releasev140.tar.gz)

3.6.1 is in https://mapbox-node-binary.s3.amazonaws.com/mapnik/v3.6.1/node-v48-win32-x64-Release.tar.gz so there might be a difference in the url were the binaries were published and how they are looked for. I'd investigate that.

@pausto
Copy link
Author

pausto commented Jul 12, 2018

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants