-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[CLEANED UP PATCH] install_name_tool in OSX Framework builds #168 #241
Conversation
shouldfix: creating a virtualenv from an OSX Framework build should no longer require XCode to run successfully. implementaion: if ``install_name_tool`` missing, download binaries from macosxforge, and install them to a temp directory rejected: download and compile .c source. TODOS: * review for python2/3 issues * cleanup of tempfiles? Assume the system will do it? * test for robustness * review implications of not having XCode for packages, if any * integrate with pypa#54 pull or its descendents. (trivial) Possible Test Code: #!/bin/sh deactivate # virtualenv on system (Framework) python # assuming I have XCode or ``install_name_tool`` in path. python virtualenv.py t_install_name_tool # creates with no issue t_install_name_tool/bin/python -c "" # remove it from path sudo mv /usr/bin/install_name_tool{,2} # should create with no issue, using tmpfile python virtualenv.py t_tmp_install_name_tool t_tmp_install_name_tool/bin/python -c "" # clean up sudo mv /usr/bin/install_name_tool{2,} command rm -rf t_{,tmp_}install_name_tool The original patch was cleaned up, tested against at Python 2.5, 2.6, 2.7, 3.2, and verified to work. Signed-off-by: Yesudeep Mangalapilly <[email protected]>
Thank you for doing more work on this everyone! |
This is currently a blocker on some of our systems. |
# TODO: Where should this get 'cleaned up', if it's a temp | ||
# install? Perhaps this should return a tuple of (path, tempdir)? | ||
|
||
import platform |
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.
Please don't use inline imports.
@gorakhargosh I've commented inline a bit. Thanks for your work so far, but this needs a bit more work. |
@jezdez I'll try to get it cleaned up. |
Signed-off-by: Yesudeep Mangalapilly <[email protected]>
Signed-off-by: Yesudeep Mangalapilly <[email protected]>
I don't have a mac, but just tried this on a friends computer, so I can't debug it. The behaviour was different - it froze for a while before failing. It's a bootstrap script, so line numbers may differ. Here is the output:
|
Many thanks for your efforts, we're happy to say we've now gone with a full Python implementation of install_name_tool added in #289. |
shouldfix: creating a virtualenv from an OSX
Framework build should no longer require XCode to
run successfully.
implementaion: if
install_name_tool
missing,download binaries from macosxforge, and install
them to a temp directory
rejected: download and compile .c source.
TODOS:
Possible Test Code:
The original patch was cleaned up, tested against
at Python 2.5, 2.6, 2.7, 3.2, and verified to work.
Signed-off-by: Yesudeep Mangalapilly [email protected]