Bill Campbell wrote:
Tried OpenPKG on Mac OS X and ran into some minor
build issues with using static libraries on Darwin...
I've got a fair number of packages running on PowerPC OS X.
I saw that it was working for Mac OS X 10.3, so I thought I'd try it...
I've found that most packages require dynamic libraries to function as
darwin/OS X just doesn't do static libraries for most things. To that
end,
I've frequently had to fiddle the .spec files to allow shared libraries
when building on darwin.
The system libraries are all shared, and it doesn't allow static apps.
But you should be able to use static libraries for your own add-ons,
a little quirk is that ld(1) will *always* prefer the dynamic version
if present. So if you have "libfoo.a" and "libfoo.dylib" in the same
location, you can't use -L/path -lfoo but have to use /path/libfoo.a
I'll probably know more once I build some packages beyond bootstrap :-)
I built a dummy package for gcc since I'm not smart enough to figure
out
how to get it to build from source.
That is probably a good idea anyway, since Apple's GCC has many more
features than FSF's GCC on Darwin. (BTW the same goes for GDB as well)
You can still build their versions from source if needed, though...
(some of it posted at http://www.opensource.apple.com/darwinsource/ )
--anders
______________________________________________________________________
OpenPKG http://openpkg.org
Developer Communication List openpkg-dev@openpkg.org
