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

updated PYTHON_INSTALL_DIR generation #636

Closed
wants to merge 3 commits into from

Conversation

wyc
Copy link
Member

@wyc wyc commented May 22, 2014

In response to #632 #635

This patch uses Python to report PYTHON_INSTALL_DIR, and it therefore allows cmake/python.cmake and python/catkin/builder.py to share most of the same code. It eliminates the debian-specific directive and works with python2 and python3. It has been tested on Gentoo, Debian, and Windows.

More testing is in order to confirm its complete functionality.

@wyc
Copy link
Member Author

wyc commented May 22, 2014

unfortunately the Travis CI build seems to fail due to a shortcoming of python's virtualenv:
pypa/virtualenv#228

@wyc
Copy link
Member Author

wyc commented May 22, 2014

looks like Travis CI was okay with that one. requesting human review now.

@wjwwood
Copy link
Member

wjwwood commented May 22, 2014

Thanks for the pull request. As you can probably imagine, we'll have to scrutinize this one pretty hard since it affects all Python packages in ROS.

I'll give some feedback soon.

@smits
Copy link
Contributor

smits commented May 22, 2014

I can confirm that the provided patch fixes #635. Thanks!!

@spaghetti-
Copy link

I would like to mention that this patch did not work for me on gentoo

Portage 2.2.28 (python 2.7.10-final-0, default/linux/amd64/13.0, gcc-5.4.0, glibc-2.22-r4, 4.4.26-gentoo x86_64) on kinetic (manual patch)

@dirk-thomas
Copy link
Member

@spaghetti- Can you please also try the follow up PR #831. And if it doesn't work provide some more information what the problem is, what the various paths are in your case in order to allow iterating on the patch.

@spaghetti-
Copy link

spaghetti- commented Nov 2, 2016

Yes of course. However @dirk-thomas is the right approach having lib/lib64 both? On my OS X install I only have lib.

@dirk-thomas
Copy link
Member

There can't be more than one location for a single package. Should it needs to be all in either lib or lib64. Each package can pick a different location though as long the Python path is set to include that path.

@dirk-thomas
Copy link
Member

I will close this as a duplicate of #831. Please continue the discussion there.

cwecht pushed a commit to cwecht/catkin that referenced this pull request Mar 20, 2018
This is preparation for ros#636. 

I noticed that there is duplicated code for loading options for the offline and GRPC offline node because they are needed while constructing the map builder for the non-GRPC offline node (and that step is the only difference between the offline node and the GRPC offline node).

I got around this by passing a map builder factory to `RunOfflineNode` instead, so we can deduplicate the code for loading options by doing it inside `RunOfflineNode`.
cwecht pushed a commit to cwecht/catkin that referenced this pull request Mar 20, 2018
cwecht pushed a commit to cwecht/catkin that referenced this pull request Mar 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants