➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Direct framework linking for MACOSX_DEPLOYMENT_TARGET < 10.3
Type: Stage:
Components: macOS Versions: Python 2.5
process
Status: closed Resolution: accepted
Dependencies: Superseder:
Assigned To: jackjansen Nosy List: bob.ippolito, jackjansen, ronaldoussoren
Priority: normal Keywords: patch

Created on 2005-01-07 10:06 by bob.ippolito, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
direct_framework_linking.patch bob.ippolito, 2005-01-07 10:06 direct framework linking patch
Messages (3)
msg47490 - (view) Author: Bob Ippolito (bob.ippolito) * (Python committer) Date: 2005-01-07 10:06 
It is not a good idea to use -framework (even with -F) if it is 
necessary to link to a less-than-current framework.  For Python, 
this is the case.

This patch to configure.in should (in theory) resolve this issue.  
Note that since only the .in is patched, autoconf must be run after 
application.

I have only tested the 10.3 scenario, but will comment as soon as 
the 10.2 build has finished and I've tested it.

Background reading:
http://bob.pythonmac.org/archives/2005/01/05/versioned-
frameworks-considered-harmful/
http://mail.python.org/pipermail/python-dev/2005-January/
thread.html#50649
msg47491 - (view) Author: Jack Jansen (jackjansen) * (Python committer) Date: 2005-01-07 13:09 
Logged In: YES 
user_id=45365

Looks good. Checked in as configure.in 1.480, configure 1.467.

Will backport to 2.4 and 2.3.
msg47492 - (view) Author: Ronald Oussoren (ronaldoussoren) * (Python committer) Date: 2006-04-17 14:31 
Logged In: YES 
user_id=580910

Bob,

Could you please close this patch, it has been applied.

Ronald
History
Date User Action Args
2022-04-11 14:56:09adminsetgithub: 41406
2005-01-07 10:06:32bob.ippolitocreate