Don't disable building Mac-specific modules for a non-framework build:

whether they crash or not is not a matter of using a framework or not,
but whether the code is run from an app bundle or not. And that it
_can_ crash (instead of tracing back) is Apple's bug anyway, not ours.
This commit is contained in:
Just van Rossum 2002-11-24 23:15:57 +00:00
parent d5169bad94
commit 05ced6aa76

View file

@ -694,20 +694,10 @@ class PyBuildExt(build_ext):
exts.append( Extension('sunaudiodev', ['sunaudiodev.c']) )
if platform == 'darwin':
# Mac OS X specific modules. Modules linked against the Carbon
# framework are only built for framework-enabled Pythons. As
# of MacOSX 10.1 importing the Carbon framework from a non-windowing
# application (MacOSX server, not logged in on the console) may
# result in Python crashing.
#
# I would like to trigger on WITH_NEXT_FRAMEWORK but that isn't
# available here. This Makefile variable is also what the install
# procedure triggers on.
# Mac OS X specific modules.
exts.append( Extension('_CF', ['cf/_CFmodule.c', 'cf/pycfbridge.c'],
extra_link_args=['-framework', 'CoreFoundation']) )
framework = sysconfig.get_config_var('PYTHONFRAMEWORK')
if framework:
exts.append( Extension('gestalt', ['gestaltmodule.c'],
extra_link_args=['-framework', 'Carbon']) )
exts.append( Extension('MacOS', ['macosmodule.c'],