Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode build system... what's the best choice?

I'm using Makefiles for most of my builds (and and applescript w/ perl) to parse them and integrate into xcode where needed

-----------------------------------------------------
email@hidden - druware software designs
http://www.druware.com
On Aug 27, 2004, at 4:02 PM, Kevin Hoyt wrote:

While that is true, I can already hear the Apple guys pointing out that we
should not be editing the project files. I believe it comes under the
heading of 'do at your own risk'

And while this can be done, the real question is about using Xcode with
external build systems such as make or gmake. What I'm looking for is a
way for me to leverage what the rest of the team is already doing. Having
them edit a Mac specific project file defeats the purpose of using gmake,
mainly, the ability to add the new file to the build system and build it
everywhere that uses gmake.

Andy Satori <email@hidden> wrote on 08/27/2004 12:43:27 PM:

Actually, the xcode project file is nothing more than an old NeXT style
.plist file, one that is easily parsed or added to on any platform.

Andy

-----------------------------------------------------
email@hidden - druware software designs
http://www.druware.com
On Aug 27, 2004, at 12:01 PM, Kevin Hoyt wrote:

Hi all,
I have a problem that I'd like to get some opinions on.

The product I work on has versions for just about every OS out there.
We
share a common codebase and all is good.

The 'problem' I have is that as new source files are added to the
product,
that are shared with the Mac client, have to be added to the Xcode
projects by a Mac developer because we are the only ones that can run
Xcode.

One possible approach to solving this is to incorporate the Mac build
process with the gmake build process we use for our Unix.  The
advantage
here is that was the gmake files are changed, Mac would get those
changes
for free.  It would also allow other developers to login to a Mac
system
so they could verify their changes.  In fact, it would mean that just
about anyone could develop on a Mac...at least for our shared code.

So, what are the disadvantages???

Well, that's where you come in...

Any comments one way or the other?
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.

_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Xcode build system... what's the best choice? (From: Kevin Hoyt <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.