[Gdal-dev] status of ldshared build? (or,
other options for OSX framework build)
William Kyngesburye
woklist at kyngchaos.com
Thu Nov 1 21:51:26 EDT 2007
In trying to figure out how to simplify the OSX framework build so
that the ngpython will work with it, it looks like libtool is simply
getting in the way - it can't make a library file with a 'lib' prefix
and '.dylib' extension. And without knowing the exact path to the
built python or installed python gdal libs (they're controlled by
distutils/setuptools), there is no way to to postprocess them into
framework binaries. I can hack libtool to generate the correct
library binary right away, but it doesn't look like this is
configurable for libtool.
One possibility is for configure to somehow get from python the exact
install path and store it in gdalmake.opt.
My other thought is to use the ldshared build, where we have complete
control over the compile and link commands configurations and build
the binary correct from the start. then the python libs link
correctly and no post-processing is needed. Currently, it looks like
the ldshared build is taylored to linux only. I recall hearing some
time ago that it wasn't really being maintained?
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/
"Mon Dieu! but they are all alike. Cheating, murdering, lying,
fighting, and all for things that the beasts of the jungle would not
deign to possess - money to purchase the effeminate pleasures of
weaklings. And yet withal bound down by silly customs that make them
slaves to their unhappy lot while firm in the belief that they be the
lords of creation enjoying the only real pleasures of existence....
- the wisdom of Tarzan
More information about the gdal-dev
mailing list