Re: No suffix, for segmented files?
Re: No suffix, for segmented files?
- Subject: Re: No suffix, for segmented files?
- From: Chris Espinosa <email@hidden>
- Date: Thu, 19 May 2005 14:05:16 -0700
On May 19, 2005, at 4:19 AM, Theodore H. Smith wrote: I want to segment some of my source files, as they are unwieldy large. I also want to list the segments in the "Groups & Files" section of the Xcode project, so I can easily get to them.
I could do this with .h. However making a file with proper source code have a .h, simply because I want to include it and not compile without prior inclusion, seems wrong, because the .h is misleading. .h means "header", after all.
I tried making the files have no suffix, and this seems to work. The file is not compiled in Xcode, even if I select the file and press command-K. This is what I want.
Is this how segmenting files should be done in Xcode? Everything seems to be working fine here, but I just wanted to check :o)
This might work, but there might be better ways to do it, all of which would leave the files with their correct .c suffix:
- Remove the files from the target but #include them from your "host" file. They get compiled once and only once.
- Leave the files in the target but move them from the Build Sources build phase to some no-op build phase (like a Copy Files phase with /dev/null as the destination). Then they'll still be full project and target members, but only be compiled at build time when #included from the host.
- Select the files and change the file type in the inspector to not be a "sourcecoode" type. The compiler should avoid them.
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