Re: Xcode dependency handling
Re: Xcode dependency handling
- Subject: Re: Xcode dependency handling
- From: Chris Espinosa <email@hidden>
- Date: Sat, 3 Feb 2007 22:29:21 -0800
On Feb 3, 2007, at 7:40 PM, Douglas Norton wrote:
Mine is the latter, as I share some common library sources with a Windows VS2005 project
MyProject ƒ WindowsStuff ƒ Window specific source ƒ headerThatIsNotSaved_WindowsImp.cpp VS2005.solution MacStuff ƒ Mac specific source ƒ headerThatIsNotSaved_MacImp.cpp Xcode.xcodeproj XPlatform ƒ XPlatformSource ƒ Headers ƒ headerThatIsNotSaved.h
Scratch up another victim. If the option in the prefs caused Xcode to save _all_ files, regardless of which project it thinks they belong too, my issue would be resolved.
After all, if I save files from another project I did not want saved at that moment, Time Machine will be my saviour, as will my source control database :).
So, to be absolutely clear: are the changes in the file not saved, that is, the file on disk is different than the file on your screen even though the "dirty" indicator is not on; or are the saved changes not causing dependencies to be rebuilt? The bug we know of with the layout you have is the latter.
The workarounds are somewhat obvious: - move the Xcode project up one level in the hierarchy so that it is peer to XPlatform - explicitly "touch" headerThatIsNotSaved_MacImp.cpp and build - clean, then build
You can file a bug report and ask it to be made a duplicate of < rdar://problem/4674054> Dependency analysis failing in case of .. in some paths, and then when that bug is fixed you'll be notified.
Regards,
Chris
|
_______________________________________________
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