From: Richard P. <ric...@gm...> - 2011-06-04 23:13:58
|
On 5/06/2011, at 12:14 AM, Dwayne Bailey wrote: > On 2011-05-25 07:17, Richard Procter wrote: >>> [...] >> I tried building and bundling PyObjC at one point but - and my memory is hazy here - it seemed to be tightly coupled to a specific version of OS X. As I abandoned the approach without looking more deeply into it, I may have overlooked something. >> > SOLVED: > > These are the things I needed to do to get PyObjC building and packaged: > > • PyObjC builds with '-isysroot /' according to the comment so that the build is portable. Rubbish. This ends up pulling in your /System files instead of the SDK you are building against. So probably not a problem if you build on 10.5 and want it to work on 10.6. But it won't work when building on 10.6 trying to ensure you are 10.5 compatible. I ended up simply commenting out sysroot where it occurred. I'm sure there are more elegant approaches, but that worked. > • You need to add the paths to the produced .eggs in your launcher > • To bundle correctly ensure you are bundling the PyObjC.bridgesupport files. Good to know! Thanks for sharing. regards, Richard. |