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.

Author brett.cannon
Recipients
Date 2004-06-26.03:41:31
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=357491

grep agrees with you, Jack:

drifty@Bretts-Computer>grep -rl PyMac_getscript *
Include/pymactoolbox.h
Modules/_localemodule.c
Python/mactoolboxglue.c

So we could just copy and paste it (and fix the spelling of Fredrik's last 
name  =).  But will those CF* functions be linked properly w/o a 
framework build?

I didn't see any macro definitions or anything to signal when a toolbox 
glue build was being done, but it would not hurt to define that.  I get a 
ton of linking errors for any module that has Carbon with this ``--
disable-framework --disable-toolbox-glue`` build that I have been 
fiddling with.  Should we try to make it so that those modules are built 
only if some flag is set somewhere signifying that the proper OS X-
specific build options are not turned off?

Or am I just being so totally non-standard with these build options (only 
done to try to build faster on my old iBook) that it is not worth the 
hassle?
History
Date User Action Args
2007-08-23 14:22:51adminlinkissue978662 messages
2007-08-23 14:22:51admincreate