Re: Distributing vs. re-using source code?
Re: Distributing vs. re-using source code?
- Subject: Re: Distributing vs. re-using source code?
- From: Allan Odgaard <email@hidden>
- Date: Wed, 15 Sep 2004 03:26:56 +0200
On 15. Sep 2004, at 0:33, M. Uli Kusterer wrote:
Since I distribute some of my apps to other people, I am often facing
the problem of having to track down all the auxiliary classes a
project uses because otherwise the recipient will be missing half the
files. And since this is reusable code, and shared between various
projects, I can't just keep them with their project either.
You can do that if you use CVS or similar. So you'd do a CVS import of
the component you want to use, this allows you to use different
versions of the same component in different projects (which is an
advantage if updating a component has the chance of breaking one or
more projects).
Another approach is to use symbolic links, add the files to your Xcode
project w/o asking it to do a copy, or put your various stuff in a
framework which you link with.
Has anyone found a solution? [...]
I think this problems plagues us all... I find that the biggest barrier
to reusability is how easy it is to reach from scratch projects, so
I've set it up so that my stuff is in the default include path (much of
my stuff is in the form of STL algorithms and containers, which are all
in the header) and new projects already have my own frameworks added to
the build process.
--
http://macromates.com/ ::: TextMate, OS X text editor
http://macromates.com/sigpipe/ ::: Personal weblog about
programming
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden