-
Notifications
You must be signed in to change notification settings - Fork 826
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
don't pollute include dir with installed submodules #4452
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4452 +/- ##
=======================================
Coverage 73.75% 73.76%
=======================================
Files 525 525
Lines 33532 33532
Branches 4139 4140 +1
=======================================
+ Hits 24733 24736 +3
+ Misses 8797 8794 -3
Partials 2 2 ☔ View full report in Codecov by Sentry. |
I see what you mean, but if one already has those dependencies installed, wouldn't they just build Lines 38 to 41 in a8d6532
|
For example, include/mapnik may contains unsupported version of |
I don't think that th 8000 is is really needed, since you should install mapnik in a extra dir, if you have conflicting versions of those, since you should never link those bits together. I do have concernce regarding the integration, since the headers now need to be included as <mapnik/protozero/...> etc. |
There is compiler flag |
i have to agree with the PR here, one might have protozero installed systemwide, which isnt the same version as the one forked by mapbox.. osrm-backend also installs some mapbox headers under my solution is to pass |
When install mapnik with bundled submodules it creates
mapbox
andprotozero
directories which could conflict with previously installed.