Preventing added files from being added to Copy Bundle Resources phase?

  • I was trying to see if I could build and use boost simply by adding the files to my Xcode project. It turns out I can (so far, anyway), but boost has a number of files with no extension, or extensions not recognized by Xcode (e.g. *.ipp). It added these to the "Copy Bundle Resources" phase, but they're all input to the compiler in some form or another.

    Is there any way to teach Xcode about these types of files, so that doesn't happen when they're added to the project?

    I'd like to tell Xcode that all *.ipp files are C++ headers, but I don't see how to do that generally, rather than per-file (especially since the file's not part of the project when it needs to know). Xcode used to have a section in prefs for defining file types, but I don't know where that went.

    I don't know how to do that for files without an extension. But are the rules for what gets added to Copy Bundle Resources configurable in any way?

    Thanks.

    --
    Rick
previous month may 2013 next month
MTWTFSS
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31    
Go to today