config.make suggests it ignores %.xcodeproj, it does not

The auto-generated project config.make says that it excludes xcodeproj folders by default, but in practice it does not appear to.

#      (default) PROJECT_EXCLUSIONS = (blank)
#
#       Will automatically exclude the following:
#
#           $(PROJECT_ROOT)/bin%
#           $(PROJECT_ROOT)/obj%
#           $(PROJECT_ROOT)/%.xcodeproj

And make output:

$ make
Compiling OF library for Release
make[2]: Nothing to be done for `ReleaseABI'.
Done!


Compiling Stingray for Release
Compiling addons/ofxIO/libs/ofxIO/src/ByteBuffer.cpp
[…]
-I./Stingray.xcodeproj/project.xcworkspace
-I./Stingray.xcodeproj/project.xcworkspace/xcshareddata
-I./Stingray.xcodeproj/project.xcworkspace/xcuserdata
-I./Stingray.xcodeproj/project.xcworkspace/xcuserdata/pizthewiz.xcuserdatad
-I./Stingray.xcodeproj/xcshareddata
-I./Stingray.xcodeproj/xcshareddata/xcschemes
-I./Stingray.xcodeproj/xcuserdata
-I./Stingray.xcodeproj/xcuserdata/pizthewiz.xcuserdatad
-I./Stingray.xcodeproj/xcuserdata/pizthewiz.xcuserdatad/xcdebugger
-I./Stingray.xcodeproj/xcuserdata/pizthewiz.xcuserdatad/xcschemes
[…]

[bilderbuchi]

thanks for the report! @bakercp @arturoc ?

I should mention this isn't a huge deal, I just filed it for completeness :0)

In my experimentation it seemed as though the % character wasn't a wildcard but instead matched subdirectories - if so, %.xcodeproj wouldn't make sense right?

[bilderbuchi]

well, it's bound to increase compilation/linking times at least, so it's worth following up, right?

Absolutely, if only to reenforce exactly how % should be used. I initially saw the line

#           $(PROJECT_ROOT)/%.xcodeproj

and after reading the rest of the block info, was confused if I could use it as a wildcard or not.

[bilderbuchi]

The makefile docs on pattern rules (apparently that's how that is called): http://www.gnu.org/software/make/manual/make.html#Pattern-Rules