[lxml-dev] lxml Mac installation idea

[Mark Bestley]

Guntsche Michael <mike at it-loops.com> writes:

> On Nov 13, 2008, at 11:33, Michael Guntsche wrote:
>>
>> Maybe others with a different setup could test this as well. Doing  
>> it this
>> way links as against the system libraries just libxml2 and libxslt are
>> taken from the static build.
>>
>
> Ah screw that. CFLAGS is not defined in every python build that's  
> available so we cannot use that.
> Honestly, this is starting to piss me off. Python modules are always  
> compiled correctly, but to get used FLAGS out of the different  
> binaries is more difficult than I thought.
> What about ALWAYS compiling a Universal Binary on 10.4 and 10.5?
>

Yep it is fun - UNIVERSALSDK is not always set either. (and on my build
setting it was a problem)

The cases I have are
1) Apple Python Leopard - nothing set but is universal
2) python.org which is universal and seems to have th flags set.
3) macports 2.5 which can be either but for this we should not build
libxml2 etc so should work anyway (I suspect Fink would be the same)

There are also 
4) manual python builds that can be for 64bit
5) 10.4 versions 
6) in theory 10.3.9
 
any more?

Possibly the best way is that if CFLAGS and UNIVERSALSDK is set then use
them otherwise compile Universal binary - From my fiddling I think this
will work for 1&2
3 works now
We need to investigate the others

But 1 & 2 are the main cases I think we need to cover - although we
ought to try 5.

I'll try some more today.


-- 
Mark