Re: [Pyobjc-dev] Error while building
Brought to you by:
ronaldoussoren
From: b.bum <bb...@ma...> - 2003-08-04 17:28:39
|
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. Can we build the objc module, then generate the files, then build the rest of the modules? b.bum |