• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Porting projects from Windows
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Porting projects from Windows


  • Subject: Re: Porting projects from Windows
  • From: Paul Walmsley <email@hidden>
  • Date: Tue, 09 Sep 2008 22:28:04 +0100

Dave Carrigan wrote:
On Sep 9, 2008, at 1:19 PM, Thomas Hauk wrote:

One method to resolve this that I've found using Google is to have all the code for all the packages lumped into a single Xcode project. At present, we have more than one application in this project, all of them using different sets of packages. Would this "monolithic" approach require me to have one Xcode project per application (resulting in a huge mess of having to manually track setting changes)? Or can I set up a single Xcode project to compile three very different applications using different sets of shared package sources?

You can add existing .xcodeproj files to a project, and set targets in that added project to be dependencies of targets in the current project. Xcode will then build the targets in the added project before building targets in your current project. I think this comes pretty close to what you are looking for.
Getting multiple projects to build and link together is something that takes a few more steps than in Visual Studio. The precise nature of it depends on what sort of projects they are (static libs, dynamic libs, frameworks). In VS you mark one project as a dependency of another and it will automatically do the dependency checks, rebuild the necessary libraries and then link the whole lot together. In Xcode there are 3 steps:

   * adding an existing project to your current project, as described above
   * explicitly add it as a dependency of the target (from the target
     info pane hit the '+' button)
   * add the output of the project to the link phase

The other issue is how you split up your targets between projects -- whether you have multiple targets in the same project (in the way you probably do with projects in a VS solution) or whether to have a single target in each project. The Xcode model is quite flexible, but I don't think it integrates as well across dependent projects as VS, as 'cross-project references' (as I believe they're called) don't work at all well in my experience for finding symbol definitions or doing type name completion.

Paul
_______________________________________________
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


References: 
 >Porting projects from Windows (From: Thomas Hauk <email@hidden>)
 >Re: Porting projects from Windows (From: Dave Carrigan <email@hidden>)

  • Prev by Date: Re: breakpoints ignored while running unit tests! Why?
  • Next by Date: RE: breakpoints ignored while running unit tests! Why?
  • Previous by thread: Re: Porting projects from Windows
  • Next by thread: Re: Porting projects from Windows
  • Index(es):
    • Date
    • Thread