best practise: make a basic project to use as library for other apps

Member
Posts: 164
Joined: 2010.10
Post: #1
i'm starting a new project using cocos3d and bullet named "dice6".
i'd like to have at the end a simulation of 6 faces dice, adn recognize what is the face "up".
when the project is finished, i'd like to use it on all the future project that uses 6 faces dices, like board game, ecc...

what is the best practise to achive this goal?
can i add to the future project "dice6.xcodeprj" and good to go, or no?

should i start any project from that project?
if i'd like to add this to old projects, should i add in the project all sources of dice6?

thanks
Quote this message in a reply
Member
Posts: 245
Joined: 2005.11
Post: #2
Well, you can't add one Xcode project to another.
Since this is likely to be quite a small project (one or two classes), you could just include the .m and .h files in other projects. Alternatively, you can build a library or framework (static libraries being the easiest way of doing things) to use in your future projects.
You may also want to look into setting up a new template, if the dependancies and things get complicated.
Quote this message in a reply
Member
Posts: 164
Joined: 2010.10
Post: #3
thanks
Quote this message in a reply
⌘-R in Chief
Posts: 1,261
Joined: 2002.05
Post: #4
(Nov 24, 2011 07:13 AM)backslash Wrote:  Well, you can't add one Xcode project to another.


Uhh, yeah you can. It's called project dependencies and they work fantastically. You build the app it automatically builds the library etc.
Quote this message in a reply
Post Reply