[Pythonmac-SIG] Someone had PIL trouble on i386 10.4.6 Python 2.4 IIRC--I succeeded this evening

[Daniel Lord]

On Apr 19, 2006, at 15:53, Christopher Barker wrote:

> Bob Ippolito wrote:
>> The libs should all be statically linked to the extensions, they
>> shouldn't be separate in the installer.
>
> Ronald Oussoren wrote:
>> I'd prefer to have fully self contained packages, and preferably
>> eggs at that. Having a shared libary makes it *harder* to  
>> independendly
>> update extensions using libpng or libfreetype.
>
> No one answered my question directly, but both Bob and Ronald have  
> spoken:
>
> It's better for each package to statically link any libs it needs
> (unless Apple provides them), even though that means that a given  
> python
> program may well end up using three copies of the same lib.
>
> Just to be totally clear: Is there any problem with the same program
> using three slightly different versions of the same lib?
NOt as far as I can tell--the libraries are statically linked so  
don't even need to be on the platform after that.
>
>> I'll have to package up my package build script one of these days ;-)
>
> What does it do? Something different than bdist_mpkg ?
By build I by hand: curl, patch code by hand, make; sudo make  
install. The libs need their make components patched to compile FAT  
binaries and PIL needed to be patched to find the .a files to link  
into its binaries. And freetype uses a confusing Jam-based install  
which had me searching for where to change it.
>
> Daniel Lord wrote:
>> I built Universal jpeg-6b, freetype2, and zlib for my current project
>> of Universal PIL. I can add libpng in easily so I'll do it.
>> So that makes jpeg, png, freetype, and zlib. What else?
>
> Those are the ones I need at the moment. Thanks! I guess a zip archive
> of the collection would be the best way to get it out there.
I'll zip up the .a files and put them on my iDisk--will send you a  
URL when ready.
>
>> I have successfully packaged up a Universal PIL for 2.4 (thanks for
>> the tips Bob;-). Packaged--not tested yet on PPC and Intel so I am
>> closer to releasing it.
>
> Post a link to it here when you are ready so we can test it.
Bob tested it and posted it already (see his email). More testing  
would be appropriate though.

> Maybe it would be helpful to have a standard way to link static libs
> with our packages. What I've done for matplotlib is create a
> "StaticLibs" directory at the same level as the setup./py, then hacked
> the setup.py to include it in the linking (and header) paths.
That sound reasonable, but not what I did--I installed them in /usr/ 
local/lib & include.
>
> I'll probably create one that has all of the above libs in it, then I
> can add a symlink to it for each package I'm trying to build.
>
> If anyone has any better ideas, I'd be glad to hear them.
>
> -Chris
>
>
>
>
> -- 
> Christopher Barker, Ph.D.
> Oceanographer
>                                      		
> NOAA/OR&R/HAZMAT         (206) 526-6959   voice
> 7600 Sand Point Way NE   (206) 526-6329   fax
> Seattle, WA  98115       (206) 526-6317   main reception
>
> Chris.Barker at noaa.gov
> _______________________________________________
> Pythonmac-SIG maillist  -  Pythonmac-SIG at python.org
> http://mail.python.org/mailman/listinfo/pythonmac-sig