forked from pypa/virtualenv
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
install_name_tool in OSX Framework builds pypa#168
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 <yesudeep@google.com>
- Loading branch information
Showing
2 changed files
with
68 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters