Re: [Pyobjc-dev] PyObjC 0.8 Release Candidate

[Bill B. <bb...@co...>]

I'm going to go ahead and change the way that automatically generated 
files are used such that it should be obvious what the 10.1 files 
should be named.  If someone can generate 10.1 headers, I would be 
happy to plug 'em in.

Given that 10.1 requires a full python installation from a third party 
and that it is very likely that the pyobjc module built for one 
installation will not be compatible with another installation due to 
linking problems, I don't think it is worthwhile to go down the path of 
building a PyObjC.pkg for 10.1.

With that said, it could be done relatively easily, if anyone so 
desires.   It should even be possible to build 10.1 compatible binaries 
on 10.2 given the way that Apple's compatibility headers work.

b.bum

On Wednesday, Dec 18, 2002, at 13:26 US/Eastern, Ronald Oussoren wrote:
> On Wednesday, Dec 18, 2002, at 17:27 Europe/Amsterdam, Jiva DeVoe 
> wrote:
>> On Tuesday, December 17, 2002, at 09:57  PM, Bill Bumgarner wrote:
>>> No, not currently.   Two issues:
>>>
>>> (1) you'll need a third party install of Python 2.2 or greater.  
>>> Fink or the MacPython community can supply such a beast.
>>>
>>> (2) you will need to regenerate the automatically generated types 
>>> and enums based on the 10.1 headers.  This is easier than it sounds, 
>>> but requires steps that have not been well documented.
>>
>> Is it documented at all?
> Not at all at the moment. Luckily regenerating isn't too hard. Basicly 
> it is:
> $ cd Modules/Cocoa && scripts/cocoa_generator.py
>
> This will generate a number of files (the '.inc' files in 
> Modules/Cocoa). Hopefully you won't have to edit the results.
>> I'll second the request for information on how to run it on 10.1.x... 
>> please point us in the right direction on this.
>
> I'd like to support 10.1.x, but I don't have time to work on that 
> right now. Patches to add that support out of the box are of course 
> welcome ;-) ;-)