Re: [2.2] Changes in unsaved header file not compiled in
Re: [2.2] Changes in unsaved header file not compiled in
- Subject: Re: [2.2] Changes in unsaved header file not compiled in
- From: "William H. Schultz" <email@hidden>
- Date: Thu, 10 Nov 2005 14:09:58 -0800
The problem is that the header file isn't specifically added to the
project. That never worked for me with 2.1 (or any earlier
version). In addition, if the case of the header file name is
incorrect in the #include, and you tell Xcode to Jump to Definition
of something in that header, it will open the header thinking it's a
file with the case specified in the #include, not the case on the
disk. Therefore, it again doesn't get saved when you tell Xcode to
build. The issue here is that Xcode is case sensitive, while the
file system isn't.
Hank Schultz
Cedrus Corporation
http://www.cedrus.com/
On Nov 10, 2005, at 1:44 PM, Stephen Chu wrote:
Just installed XCode 2.2 and find something odd right away.
I made some changes in a C++ header file and then rebuild the
project before saving the file. The file is not automatically save
even though I have Always Save in preferences. And the compilation
is still using the copy on the disk instead of the one in editor
window.
Maybe it's because this header file is not specifically added to
the project. But this used to work in 2.1. Took me some time to
finally figure out why I was still running the old code.
--
Stephen Chu <mailto:email@hidden>
Rampage Systems, Inc. <http://www.rampageinc.com/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40cedrus.com
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