I have a hard time deciding, which direction to go with the a project
that I'm currently porting. It's a standard autotools project that
creates four libraries that belong together. Now, since this is a
project coming from the unix world, many user/developers will have
dependent projects that expect standard linux setup, e.g. libraries
in /usr/lib and headers in /usr/include. On the other hand, it would
be nice to have an option for a more Mac-like setup.
There are a couple of Makefile rule variants floating around that
create frameworks from dynamic libraries. However, since we have four
libraries here that share a good part of their headers and
documentation, it looks to me that four interdependent frameworks are
not the greatest idea. On the other hand, Apple's developer
documentation states that umbrella frameworks are to be avoided.
There is also the option to link all object files together to one big
framework. But this would break the whole Makefile setup and
complicate everything.
Now, what to do?
a) stay with dynamic libs and forget about frameworks
b) build four distinct frameworks
c) ignore the warning and build an umbrella framework
I would be glad to hear your opinions,
Mark
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Unix-porting mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
