shared subproject, subversion, xcode
shared subproject, subversion, xcode
- Subject: shared subproject, subversion, xcode
- From: Charlton Wilbur <email@hidden>
- Date: Tue, 9 Aug 2005 19:52:54 -0400
All,
I have a situation that I expect some of you have run into, and I'd
like advice on best practices.
I have some code that provides a lot of useful functionality. It so
happens that it's in Cocoa, and provides a few of the features I
really missed from Perl when I started working with Objective-C, but
I don't think that's relevant to this question. Eventually (once
I've used it and am satisfied that it's as good as it's likely to
be), I'll release it under the BSD license.
Now, this is currently its own repository in Subversion and its own
project in Xcode. What I want is to have it remain a separate entity
entirely, so that I have one authoritative version of the source, but
to have it be available to other projects.
What's the best way to go here? Framework? (It doesn't seem like
there's enough there to make it worthwhile, and I'm not concerned
about revealing the source when I release it.) Copying the source
and adding it to other projects? (It seems like that would play
merry havoc with source control.) Subprojects with external
references to the other code's Xcode project? Some other way I'm not
aware of?
Thanks for any advice,
Charlton
--
Charlton Wilbur
email@hidden
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden