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

Boost MSVC 2019 Compile Issues #124

Closed
dpaulat opened this issue Jul 11, 2021 · 9 comments
Closed

Boost MSVC 2019 Compile Issues #124

dpaulat opened this issue Jul 11, 2021 · 9 comments

Comments

@dpaulat
Copy link
Contributor

dpaulat commented Jul 11, 2021

vendor/boost has compile issues when compiling with MSVC 2019. See mapbox/mapbox-gl-native-boost#2. I can think of two potential resolutions:

  1. mapbox-gl-native-boost needs forked
  2. Use a package manager (e.g., conan)

The latter could also help with other missing dependencies (e.g., zlib), if the project wants to move in this direction.

@kiibimees
Copy link
Contributor

Conan might introduce annoying yet-another-tool-dependency. Forking and updating mapbox-gl-native-boost seems to be a clean enough soution, IMHO. Any dependency to Mapbox should be removed in the future anyway, I guess.

@kiibimees
Copy link
Contributor

Or why not just copy and commit all boost files directly into this repository? Boost itselt doesn't have a 'release' repo and I don't see any good reason why should we create it and make things more compicated. It's a header-only usage.

@dpaulat
Copy link
Contributor Author

dpaulat commented Dec 10, 2021 via email

@kiibimees
Copy link
Contributor

Sure, fine by me. Could somebody with enough ranking do it in the near future? Right now MSVC 2019 build fails because of that.

@dpaulat
Copy link
Contributor Author

dpaulat commented Dec 10, 2021

If you're looking for a temporary solution while waiting for the fork, I fixed the immediate issue in a fork, without upgrading boost:

https://github.com/dpaulat/mapbox-gl-native-boost

@kiibimees
Copy link
Contributor

Well, it would be nice if I could just point QtLocation submodule to a maplibre state where it is fixed. In that case one can compile the plugin more easily. An super-cool would be if somebody could review my merge request. That makes short URL-s and styles also work with the plugin. Then I would be very happy for the start. Later, I would like to handle style types (streets, hybrid, terrain, etc) more correctly but that is not a showstopper anymore.

@kiibimees
Copy link
Contributor

It would be nice if somebody with enough ranking, fork the mapbox boost repo and add at least the MSVC fix.

Anybody?

@kiibimees
Copy link
Contributor

kiibimees commented Jan 6, 2022

I would be so much appreciated if somebody could fork the Boost repo and apply necessary fixes. Anybody?

@dpaulat
Copy link
Contributor Author

dpaulat commented Apr 20, 2022

Resolved by #231 (commit 1398333)

@dpaulat dpaulat closed this as completed Apr 20, 2022
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