Fix usage with recent libosrm versions #259
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
deaf5d3 to
8070da2
Compare
|
I just rebased the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
As part of the discussion in #256 it turns out the way the
osrm::EngineConfigobject is initialized inlibosrm_wrapper.cppdoes not work with recentlibosrmversions.This PR contains a simple fix for this + maybe some further changes when we can figure out the rest of the problem in #256. cc @KieCap
Tasks
osrm::EngineConfigobject in a way that is compatible with recentlibosrmversionsCHANGELOG.md