Re: [Pyobjc-dev] Error while building

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

On Monday, 4 August, 2003, at 19:28, b.bum wrote:

> On Monday, August 4, 2003, at 13:24, Ronald Oussoren wrote:
>> The CodeGenerator script tries to import objc and uses 
>> 'objc.lookUpClass' to detect if a typename denotes a class, if objc 
>> cannot be imported it uses a static list for that. That static list 
>> must be complete if we want to support installation of a complete 
>> PyObjC without a prior PyObjC installation, and therefore the import 
>> of objc shouldn't buy us anything. I'll update the code.
>
> Sounds like PyObjC has evolved to the point of needing pyobjc to build 
> pyobjc;  kind of like emacs builds temacs to gain access to a lisp 
> engine prior to building the full app... or the way gcc bootstraps 
> itself.

This actually is some very old code, I already had a mosty working 
bridge when I tackled wrapping global functions.

>
> Can we build the objc module, then generate the files, then build the 
> rest of the modules?

I don't think this is worth the trouble. You'd have to do difficult 
things with distutils to make this work.

I'm currently checking in a patch that removes the optional dependency 
on an installed PyObjC.

Ronald