Re: Headers end up in "Resources" folder
Re: Headers end up in "Resources" folder
- Subject: Re: Headers end up in "Resources" folder
- From: "M. Uli Kusterer" <email@hidden>
- Date: Fri, 27 Oct 2006 12:09:41 +0200
On 26.10.2006, at 20:39, M. Uli Kusterer wrote:
I have a project that's been converted from CodeWarrior to Xcode
ages ago, and it has one problem: When I add a header, it
automatically gets added to the target, and the headers end up in
the build product. Now, I can manually uncheck each and every
header file when it's added to the project, but since this is a
complex project with lots of headers, I would really like to "fix"
this project not to add the headers at all.
If I create a new project, header files added to it don't even
*have* the "target membership" checkbox, but they have the same
file type (sourcecode.c.h), and all the roles etc. in the project
seem to be the same.
Does anyone know what causes Xcode to hide the target membership
checkbox in new projects and how I can fix that for hours?
Okay, thanks to Eric Eizenman for mentioning the "Copy Files"
phase. At least I now know why my project has the "add to target"
checkbox for headers and new projects don't: As soon as you add a
"Copy Files" build phase, the checkbox gets added to headers. I don't
quite see why one would want that, considering there is a separate
"Copy Headers" build phase, but at least now it's reproducible, and I
know that it's nothing screwy with the project file.
So, the only option I have is manually removing each header from
all targets, because everything else just doesn't work for this
problem. The "Copy Headers" phase that doesn't copy anything is a
workaround for smaller projects, though.
Cheers,
-- M. Uli Kusterer
_______________________________________________
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