Re: How to convert a project using legacy build location to modern?
Re: How to convert a project using legacy build location to modern?
- Subject: Re: How to convert a project using legacy build location to modern?
- From: Quincey Morris <email@hidden>
- Date: Thu, 05 May 2016 21:31:10 -0700
- Feedback-id: 167118m:167118agrif8a:167118s7MRcrEMnv:SMTPCORP
On May 5, 2016, at 20:21 , Bernie Maier <email@hidden> wrote:
how on earth did Xcode 7 know that this particular old project that I inherited wanted to build inside inside the source tree, given that I have never configured Xcode 7 to use legacy build locations
There is (I had forgotten about it) a whole “Build Locations” section in the actual project settings, which defaults to setting things relative to the project-um-workspace setup for the build location, but can (IIRC) also be set to absolute paths, or paths relative to something else.
I guess Xcode does something rational with the build settings when you open an old project. It’s a little mysterious, because until fairly recently the Xcode project was always in a 3.2-or-earlier-compatible format, which meant that whatever you put in the project-um-workspace setup would somehow be respected by Xcode 3(!). But I can’t pretend to want to know exactly how it works, or worked.
|
_______________________________________________
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