My application contains multiple sub folders, that can go quite deep, e.g.
(this is just a fictive example)
If another part of my application needs an include file of this folder it writes this:
The problem is that if the file that contains this include is also in a quite deep path, like this:
And we have checked out our project in the folder:
Then the Visual Studio compiler (we compile using the
/I. (slash-I-dot) option) first looks for the file in this location:
And then only in
(this behavior is described in http://msdn.microsoft.com/en-us/library/vstudio/36k2cdd4(v=vs.100).aspx).
So it insists in looking first in the place where the compiled file is, and then only looking at the
The problem is that the place where the compiler looks first results in a filename that is too long (>256 characters) and the compiler just gives up.
Is there a way to tell Visual Studio to not stop when an include path is too long? Preferably without using the bracket include format (
You can just make file in interestgroups folder that only include config.h file and you just include interestgroups file and use that file