Re: project-relative precompiled headers
Re: project-relative precompiled headers
- Subject: Re: project-relative precompiled headers
- From: Scott Tooker <email@hidden>
- Date: Wed, 23 May 2007 18:47:20 -0700
Please file a bug.
Scott
On May 23, 2007, at 3:35 PM, Stuart Smith wrote:
We sometimes build different branches (from our source code control
system)
of our projects on the same machine at more-or-less the same time.
If the
precompiled headers of the branches differ, but are at an absolute
location,
one branch or other will fail to build because it is using the wrong
precompiled headers.
This is related to the problems others have had with moving a
project to
another machine.
So, we took the list advice and changed the Precompiled Headers
Cache Path
to something project-relative, on our case that's
../Output/SharedPrecompiledHeaders.
This works fine, but now all our developers are reporting the
presence of a
new, empty folder called SharedPrecompiledHeaders in a new folder
called
Output at the top level of their boot disks. Benign, but irksome.
Did we
miss some magic incantation, or is this a bug? - if the latter, I'll
report
it.
Stuart
_______________________________________________
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
_______________________________________________
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