Re: [Pyobjc-dev] 2.2.x / non-framework build update

[Ronald O. <ous...@ci...>]

On Tuesday, Sep 24, 2002, at 16:30 Europe/Amsterdam, Bill Bumgarner 
wrote:

>
> I just did a bit of an experiment and was successfully able to run the 
> TableModel example against Python 2.2.1 using the standard system 
> supplied version of Python.
>
That's great. Did you have to change much in the pyobjc code?
>
> I am going to invest some time into putting together a template 
> Py-Cocoa project that uses a standard distutils style build formula to 
> build a working, standalone, Cocoa application without requiring 
> anything but the pyobjc module and the standard Python 2.2 that ships 
> with OS X.

If you find time to implement this I'm all for replacing the build 
script I wrote, as you said I'm depending on some legacy code that 
should not be necessary.

>
> There are three primary challenges:
>
> 	- generating an appropriately configured plist.  This is trivial, 
> really.
Not entirely trivial but close enough... I'd either like to see 
integration with PB or a standalone tool for editing the plist file. 
Plist files for document based applications are pretty simple, but I 
don't like to edit the XML by hand.

>
> 	- putting something together that can be easily managed through 
> project builder.   I can't think of anything hard here.
;-) that was what I thought when I started on my PyObjC updates ...
> 	
> 	- building a tiny bootstrap binary that can be stuck in the .app 
> wrapper and be used to bootstrap the python interpreter with the 
> appropriate script & arguments within the app wrapper.  This is 
> actually pretty trivial, as well.
Wouldn't the python binary in MacPython (aka the framework install) be 
usefull here? Please try to build something that allows access to the 
Carbon API's

Ronald