-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
Get --with-next-framework to work again (on OSX at least) #34952
Comments
These patches to Makefile.pre.in, configure.in and Modules/getpath.c make --with-next-framework work again, for build as well as install. At least 50% of the credits go to Tony Lownds (as they say: the bits that show a strike of genius are his, the stupidities are mine:-) --with-next-framework now has an optional argument saying where to install the framework (default /Library/Frameworks). Using --with-next-framework will also automatically set $prefix correctly. Makefile.pre.in will create a temporary skeleton framework in the build directory against which python.exe is linked and which is used when python is run from the build directory (for building the extensions, for instance). "make frameworkinstall" will install the complete framework (including Lib/python2.2 and all that jazz) in the final location. getpath.c now expects a "normal" python installation even in a framework, and it has also acquired (framework only) a bit of magic to detect that it is running with the skeleton framework from the build directory. The main reason for posting the patch here is that there's quite a bit of changes, and I can never be sure that it doesn't break things on other platforms. Assigned to Martin because he's one of the config purists and has provided valuable feedback before. |
Logged In: YES Please see As for the specific patch:
|
Logged In: YES Ok, attached is a new patch which should address the issues you've raised:
Also a few minor things were changed to make building the |
Logged In: YES The patch looks technically fine now, also I still cannot Also, you might recheck the likelyhood that |
Logged In: YES As to the utility of frameworks: did you see my pythondev-post? Not convinced??!? As to OpenStep, Rhapsody and naked Darwin: I have absolutely no way of checking that. But, all that aside: did you check that these mods don't break builds on your system? |
Logged In: YES Please see The code itself works fine on Linux, no worries here. |
Logged In: YES Checked in the changes, with most of Martin's suggestions These versions of Makefile.pre.in and configure.in should definitely be tested for ill effects on other unix platforms. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: