{"action":"created","issue":{"url":"https://api.github.com/repos/Project-OSRM/osrm-backend/issues/2033","repository_url":"https://api.github.com/repos/Project-OSRM/osrm-backend","labels_url":"https://api.github.com/repos/Project-OSRM/osrm-backend/issues/2033/labels{/name}","comments_url":"https://api.github.com/repos/Project-OSRM/osrm-backend/issues/2033/comments","events_url":"https://api.github.com/repos/Project-OSRM/osrm-backend/issues/2033/events","html_url":"https://github.com/Project-OSRM/osrm-backend/issues/2033","id":137446647,"number":2033,"title":"Provide an \"osrm-config\" command as alternative to pkg-config","user":{"login":"springmeyer","id":20300,"avatar_url":"https://avatars.githubusercontent.com/u/20300?v=3","gravatar_id":"","url":"https://api.github.com/users/springmeyer","html_url":"https://github.com/springmeyer","followers_url":"https://api.github.com/users/springmeyer/followers","following_url":"https://api.github.com/users/springmeyer/following{/other_user}","gists_url":"https://api.github.com/users/springmeyer/gists{/gist_id}","starred_url":"https://api.github.com/users/springmeyer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/springmeyer/subscriptions","organizations_url":"https://api.github.com/users/springmeyer/orgs","repos_url":"https://api.github.com/users/springmeyer/repos","events_url":"https://api.github.com/users/springmeyer/events{/privacy}","received_events_url":"https://api.github.com/users/springmeyer/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-03-01T02:31:48Z","updated_at":"2016-03-01T15:59:44Z","closed_at":null,"body":"It is great that osrm-backend provides a libosrm.pc for use with pkg-config because it is foreseeable that various tools might use this.\r\n\r\nHowever the pkg-config support was originally created for the use of node-osrm and ideally node-osrm would depend not on pkg-config but rather a custom named command called `osrm-config`. The reasons are:\r\n\r\n - Having an extra dependency on pkg-config is annoying when all node-osrm needs is a few things like library and include paths\r\n - When osrm-backend is installed in a custom location to be able to use pkg-config the PKG_CONFIG_PATH needs to be set.\r\n\r\nProviding an `osrm-config` would make things better by:\r\n\r\n  - Reducing another dependency of the node-osrm build\r\n  - Allowing only PATH to be set to point at a custom `osrm-config` location (and not having to set PKG_CONFIG_PATH).\r\n"},"comment":{"url":"https://api.github.com/repos/Project-OSRM/osrm-backend/issues/comments/190783933","html_url":"https://github.com/Project-OSRM/osrm-backend/issues/2033#issuecomment-190783933","issue_url":"https://api.github.com/repos/Project-OSRM/osrm-backend/issues/2033","id":190783933,"user":{"login":"TheMarex","id":606968,"avatar_url":"https://avatars.githubusercontent.com/u/606968?v=3","gravatar_id":"","url":"https://api.github.com/users/TheMarex","html_url":"https://github.com/TheMarex","followers_url":"https://api.github.com/users/TheMarex/followers","following_url":"https://api.github.com/users/TheMarex/following{/other_user}","gists_url":"https://api.github.com/users/TheMarex/gists{/gist_id}","starred_url":"https://api.github.com/users/TheMarex/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/TheMarex/subscriptions","organizations_url":"https://api.github.com/users/TheMarex/orgs","repos_url":"https://api.github.com/users/TheMarex/repos","events_url":"https://api.github.com/users/TheMarex/events{/privacy}","received_events_url":"https://api.github.com/users/TheMarex/received_events","type":"User","site_admin":false},"created_at":"2016-03-01T15:59:44Z","updated_at":"2016-03-01T15:59:44Z","body":"> Having an extra dependency on pkg-config is annoying when all node-osrm needs is a few things like library and include paths\r\n\r\nI don't see this as a big dependency - `pkg-config` is pretty lightweight itself. We can assume `pkg-config` exists on the platforms we want to support. Windows is somewhat of an oddball here, but we are not running this in production anyway. Having Windows support in our backend only is there to be resilient against compiler specific behavior. We don't really need `node-osrm` packages.\r\n\r\nI see setting `PKG_CONFIG_PATH` as easier than support yet another build system layer. I don't think we should move forward here. We might have a documentation hole w.r.t. `PKG_CONFIG_PATH` in `node-osrm` and we should probably run a check and error if `pkg-config libosrm` does return a not-found."}}