Re: options for generating pbxproj files
Re: options for generating pbxproj files
- Subject: Re: options for generating pbxproj files
- From: Mike Jackson <email@hidden>
- Date: Sun, 6 May 2007 10:30:23 -0400
I agree with Chris on this. If you have a working build system on
Linux based on Jam/Makefile then there is a really good chance that
that same build system will work on OS X and will be easier for you
to maintain in the long run.
I guess a philosophical question about the project come to mind?
Is this an OpenSource Project? If so then some mac developers will
cry for Xcode projects. If NOT then you only have yourself and co-
workers to keep happy with the build system. If everyone is happy
with a jam/make based build system then by all means use it. Just
because you are not using Apple's IDE on OS X does not mean you are
any less of a Mac Developer or anything else. You should use what
works for you and your company. If that is Jam/Make then by all means
use it. I think the important goal is to get your Application running
under OS X. How you get to that goal is up to you.
I personally use CMake for my project mangement. I have to
compile on everything from OS X to XP to IRIX to 64Bit Linux to a
Cray X1. CMake does that for me and does it reasonably well. The
xcode projects that are generated work just fine. So do the
VS2003/2005 projects that are generated on a Windows machine. I also
use Eclipse/CDT for everyday development but use Xcode when I need a
good debugger on OS X. I just have Cmake generate an xcode project on
demand and then debug. (The Eclipse/CDT debugger can get 'odd' after
a bit). This system seems to work find for myself and the other
developers on the project.
Just my two cents worth of perspective.
--
Mike Jackson Senior Research Engineer
Innovative Management & Technology Services
On May 6, 2007, at 7:38 AM, Chris Hanson wrote:
Now I'm curious as to why you're even using Xcode for this project,
rather than just using make or jam as you must be on Linux. What's
the reason for it?
A large number of developers do run very large cross-platform
projects where they manage Xcode and Visual Studio projects by
hand. They also operate under constraints such as always getting
clean builds that pass all unit tests from the main line of
development in their source repository. And so on. The
differentiating factor is that typically in such projects, the
developers working on them only expect code to be built once it's
added to an IDE project file, not as a side-effect of existing in a
particular directory. This is in contrast to some makefile-driven
projects, where everything that can be identified as a source file
in a particular directory or subdirectory gets built. (Other
makefile-driven projects work more like IDE projects, and
explicitly state what to build.)
Since it sounds like you're maintaining an environment where you
want to build whatever is in a particular directory, and you
already have an infrastructure for doing so on Linux, the path of
least resistance may be to use the same technique on Mac OS X.
Especially if you're never actually *using* Xcode and are just
using it to create project files to build.
-- Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com
This email sent to 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