-
Notifications
You must be signed in to change notification settings - Fork 280
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
[Windows] make more relocatable wrapper #1086
[Windows] make more relocatable wrapper #1086
Conversation
Please target the default branch with any changes. |
a11153e
to
3620f4e
Compare
Done. Btw, a little bit off-topic, are you open to add GitHub workflow to run the basic Windows CI for catkin? I can work on that. |
Thanks for the feedback. The new iteration is ready for review. |
f5d5431
to
c71c042
Compare
Thanks for the patch. |
@dirk-thomas Thanks for the merge! And it would be great this can be cherry-picked to |
* relocatable wrapper. * address the feedback. * address the feedback. * correct the usage.
Cherry-picked to |
This pull request is to remove a compile time variable dependency to
@PYTHON_EXECUTABLE@
variable. This is motivated by trying to relocate an existing ROS installation to a different location in Windows, where one can either use tool (e.g.,conda
) or its own script to patch the hard-coded paths for the plain-text files (e.g.,python
scripts, CMake files,pkg-config
files, etc.)However, it is challenging to patch the string literal baked in binary files. So I turned to see why it is not an issue for
setuptools
wrapper. By reading the launcher code, I realized that it reads the SHEBANG line and use it as the hint ofPython
runtime location, and fallback to simply usePython.exe
if none is specified or found. By this approach, the binary doesn't have the dependency to the compile time variable, and we can be more close to makecatkin
installation relocatable (at least with existing tools' help).