Skip to content
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] Accommodate different drives for --root #1071

Merged
merged 2 commits into from
Mar 19, 2020

Conversation

seanyen
Copy link
Contributor

@seanyen seanyen commented Mar 19, 2020

This is a follow-up fix for #1070

In cases of that CMAKE_INSTALL_PREFIX resides in the different drive from the source code, the previous fix will result in the Python module to be installed at the same drive where the source code sits. For example, if ROS source code is checked out on C: drive and cmake install into D:\opt\instsall, the Python module will be mistakenly installed to c:\opt\install\.

This pull request is to take the target drive into consideration. And hope this can be cherry-picked into kinectic-devel.

@seanyen
Copy link
Contributor Author

seanyen commented Mar 19, 2020

@dirk-thomas This is ready for review and merge. Thanks for your feedback on the drive name thing. Problem do manifest when the source workspace is on different drives from the install space.

@dirk-thomas
Copy link
Member

Thanks for the patch.

That was exactly what I was concerned about in the previous patch: #1070 (comment)

@dirk-thomas dirk-thomas changed the title [noetic][Windows] Accommodate different drives for --root [Windows] Accommodate different drives for --root Mar 19, 2020
@dirk-thomas dirk-thomas merged commit 6a927bc into ros:noetic-devel Mar 19, 2020
dirk-thomas pushed a commit that referenced this pull request Mar 19, 2020
* accommodate different drives.

* revert extra changes.
@dirk-thomas
Copy link
Member

Cherry-picked to kinetic-devel: 39bbd52.

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

Successfully merging this pull request may close these issues.

2 participants