Re: private frameworks
Re: private frameworks
- Subject: Re: private frameworks
- From: Daniel Todd Currie <email@hidden>
- Date: Mon, 29 Mar 2004 12:05:29 -0800
All the responses I have received from my previous post and all of
information that I have dug up in the archives, etc., suggest that the
only way to include a private framework in an application bundle is to
create a second target and build the framework at the same time as the
application.
What if I don't want to have to build the framework with every app I in
which I use it? What if I don't want to hassle with all of the
framework resource files and adding multiple targets to every app I
make? I certainly don't have to build the Cocoa framework every time I
build an app, so why should this be any different?
What I really want to do is build a framework bundle once, and then
have a single file that I can easily dump into any application project,
and then just add a new copy file build phase to insert the framework
into the application bundle. Is this really such a bad idea? Is it
really so hard to do? This seems to me to be far more intuitive than
trying to manipulate all of the multiple nibs, plists, image files,
that come along with each framework. The current private framework
methodology reminds me of the boorish days of procedural programming.
Encapsulation, anyone?
-- Daniel Currie
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.