I hope this is not too OT. I am after some advice on how to organize projects best.
Let's say I have project that has - a preference pane - an agent app - a user application - some shared code between them Right now I have a top project with just an aggregation target. I has references to all (sub)projects. The common parts are currently in a framework and is linked from the preference pane, the agent app and the application. Now the common part only exists for code organization reasons. I could have as well just referenced the files from the different projects directly. Going the embedded framework route feels a little cleaner ... but also a little too much for the little shared code. Any wise words on this? How would you approach this? Is there a way of statically linking a framework (and not just a library)? cheers -- Torsten _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
