Skip to content
This repository has been archived by the owner on Jun 8, 2024. It is now read-only.

Adapting to differently named boost libraries #27

Closed
springmeyer opened this issue Dec 20, 2013 · 3 comments
Closed

Adapting to differently named boost libraries #27

springmeyer opened this issue Dec 20, 2013 · 3 comments

Comments

@springmeyer
Copy link

Boost libs sometimes have -mt at the end to signify they are the multithreaded versions. After Project-OSRM/osrm-backend@4a3db7e node-osrm now needs to link all dependent libraries so we need to know their exact name.

So, builds against homebrew based boost will start failing at 1c51388 until we come up with a solution.

Possibilities are:

  • depend on OSRM to provide a pkg-config that provides all library names
  • come up with some custom node-osrm script to find and detect boost library names

I think pkg-config is ideal, just need to start testing this post Project-OSRM/osrm-backend@8383222

@springmeyer
Copy link
Author

work in progress at #28.

@DennisOSRM - after merging can you test the build against homebrew libraries? (I don't use homebrew currently for boost).

@jfirebaugh
Copy link
Member

#28 seems to be working for me with homebrew.

@springmeyer
Copy link
Author

thanks for testing @jfirebaugh - closing this now as #28 has landed.

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

No branches or pull requests

2 participants