Hi,
I think I found a bug with VS, and I've included a project
example of the problem I got.
I've got a project deep into a set of folders. The project
have an additional include library directory which is
pretty long and expressed relative to the project
(with ..\..\ and directory names).
I've got an #include in a source file that tries to
include the file in a distant directory. That include
works fine in DEBUG mode, but in RELEASE mode VS.Net says
it cannot include the file because it hasn't found it. The
two configurations (debug and release) have the exact same
additional include directories.
I've found out that by adding debug information to the
database (Program Database for Edit & Continue (/ZI)),
thus disabling optimization, the file is included and
everything work. That leads us to a problem: we
definitively want the project to optimize.
If you deplace the include file three directories up (and
that you change the #include path), the file is included
and everything works.
I've got a test project I've done to help understand the
problem. You can grab it at
http://www.geocities.com/kiroke2/IncludeProb.zip
Extract everything directly on your drive. Open the
project situated in the 123456789 folders. The include
file is in the 987654321 folders.
Is this a known issue? We really need that much folders
and we need to optimize the release configuration.
Thanks,
Francois
