Automated or simpler cross/platform project format management
Automated or simpler cross/platform project format management
- Subject: Automated or simpler cross/platform project format management
- From: Tobias Ford <email@hidden>
- Date: Mon, 19 Jun 2006 01:44:11 -0500
Let me first describe what we have for set up for windows and linux:
For windows we have a root solution that includes all of the sub-
libraries that are defined in their own libraries. These library
projects are updated whenever someone adds new cpp and header files
by running a perl script that automatically traverses the directory
and adds all files that it finds in the directory to the library
project file. For Linux, it's pretty much similar with the only
exception being that these files are instead added to appropriate jam
file includes that are then updated with a post buildJam.pl script
that creates the master build file.
Another friend from work had done some of the initial work of getting
our game up and going under OSX. Unfortunately, he did most of this
through the command line using jam files. He had spent some time
looking into where my question is going and wasn't able to find a
decent solution, hence his choice to using the command line. I'm not
so keen on doing the command line thing for development, though.
It's very important to us to be able to maintain the build across all
platforms at all times. Using our build scripts, anyone can add new
files and guarantee that at least the projects will work and keep
others from being blocked (if only VC++ was on par of gcc with code
errors).
Looking at the xCode project file format... It's readable, but is
lacking in simplicity for building and maintaining through an
external script (especially with what appears to be all of the unique
hash ids). I know that xCode supports external legacy projects, but
my understanding is that the included files won't show up in the
Groups and Files project pane (I could be totally wrong, though
because of little knowledge with dealing with legacy apps).
I'm wanting to find a solution that is maintainable by people that
are not on the platform and through automation (build scripts) while
still allowing full support of all of the xCode features for all of
us that prefer to work under OSX while avoiding command line jam builds.
Has anyone else dealt with this type of a project maintenance problem
and come up with a decent solution? I'm hoping to not reinvent the
wheel if someone else has already done it. I would really appreciate
any suggestions or pointers.
Thanks.
-------------------
Tobias Ford...
tobias1482 'at' mac.com
tford 'at' spacetimestudios.com
-------------------
Sr Programmer @ space time studios for a generic space game mmo
"The Batman is Muhhammed Ali -- Jim Brown -- Shaft -- an' Super-Fly
all rolled into one!" -- Batman #250 by Frank Robbins
_______________________________________________
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