-
Notifications
You must be signed in to change notification settings - Fork 660
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
replace the python version finding mess with cmake builtins #2931
Conversation
docker/Dockerfile-run
Outdated
@@ -30,7 +30,7 @@ RUN rm -f valhalla_*.debug | |||
RUN strip --strip-debug --strip-unneeded valhalla_* || true | |||
RUN strip /usr/local/lib/libvalhalla.a | |||
# TODO: fix https://github.com/valhalla/valhalla/issues/2929 and update this line |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# TODO: fix https://github.com/valhalla/valhalla/issues/2929 and update this line |
i kind of prefer the |
Well, yeah I agree for valhalla (and other self-contained/-built apps), but if you think about it more, it actually makes sense to let the python framework you're using to build the bindings tell you where to install them. It installs to /usr/local if your python installation is also at /usr/local. And if you force the install to /usr/local, a regular python won't be able to find it by default, you'd have to alter the |
i still think
but as i mentioned im totally cool with tackling that later |
Huh, you're right, thought I checked it on ubuntu. Maybe I did it on my arch, where /usr/local is not in the sys.path (or in the default linker paths, guess they go together).. I have less strong feelings about it in that case:) |
fixes #2929
it uses the "new" CMake builtin approach to get the right python lib path from the actual python installation used to build the bindings. Meaning it'll install now to
/usr/lib/python3/dist-packages/valhalla
instead of/usr/local...
, but that's actually better IMO