Re: Adding externally managed sources to a project
Re: Adding externally managed sources to a project
- Subject: Re: Adding externally managed sources to a project
- From: Jens Alfke <email@hidden>
- Date: Sat, 15 Sep 2012 09:40:23 -0700
On Sep 15, 2012, at 7:54 AM, David Mirabito < email@hidden> wrote: So each item under XCode/ ended up being it's own little git repo
I personally would avoid creating the Git repos — it seems confusing to have two different version control systems in play, especially since Mercurial offers nearly all the same functionality as Git (except for the IDE integration, sadly.) You still need to add all the Xcode projects and resources to Mercurial anyway to get them checked into the main project, right? I am just wondering if there's any tips for this kind of workflow? In particular adding new files means dropping to a terminal, creating the .c or .h, then back to XCode and add references to the files.
Why can’t you create the file using Xcode’s New command? Granted, you’ll still need to leave Xcode at some point to add it to Mercurial, but you can do that for all the new files in one step when you’re ready to check in by running “hg addremove” in the project root dir. Is there some way to tell a project to "reference all .c in this dir" without having to manually add files?
I’m pretty sure there isn’t. :( Or some way I could 'make refresh' to poke the references in myself?
There are some cross-platform ‘make’-like tools that will generate Xcode projects from a build configuration file. Google’s GYP is one, and I think CMake is too. These can be very useful if you have a huge and complex cross-platform project, because you only have to define your list of source files once, but in my experience they’re fairly complex to learn and configure.
—Jens |
_______________________________________________
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