On Mon, May 12, 2008 at 11:26 AM, Stefan Behnel <stefan_ml@behnel.de> wrote:
Likewise, macports doesn't provide static libraries for the libraries it installs, and the docs don't hint at anyway to get it to do so.
Great! Now that would have been too easy anyway, wouldn't it? :-/
Thanks for the infos. Now, anyone for a plan B?
It looks to me like the typical way to do this in an OS X app is to compile your static libs then bundle them with your application (and as Mike pointed out, Apple does not recommend this). Obviously there is a ram penalty for that (the custom lib). I don't see lxml distributing static libs just for OS X :) The best thing I can think of is to get --static working for libxml2.a files and then I can submit to you the steps I took to build my static libs from source (assuming I can get that all to work). Would that be useful? If it proves too cumbersome I might just continue to use the DYLD_FORCE_FLAT_NAMESPACE var at runtime even though that's bound to bite me someday. Unlike Mike I am fortunate enough not to be using lxml in *production* on OS X ... yet also misfortunate enough to be the only one who sees segfaults :( K