Our current project configuration maintains most properties in .txt files referenced from the "additional options" block of the command line section of a C++ project properties page. These .txt files contain additional include directories, but they are apparently not parsed by VAX. This means that pressing alt-g on a filename that is relative to one of these include directories fails, and suggestions do not work relative to these directories when writing an #include directive.
I'm pretty sure VAX works properly when these include paths are listed directly in the "General" section, but when you have a lot of projects that need the same settings it's easier to maintain externally.
Unfortunately, VA does not currently support @ compiler response files. We are planning to implement this at some point:
case=718
For now, something you could try would be to enable the "If solution is not empty" checkbox on the
Projects -> File Handling
page of the VA Options dialog. The first time you open a file from one of your include directories, VA will parse all the files in that directory. This option is off by default. Once the files have been parsed, they will be cached until the symbol db is rebuilt (usually this only happens when you install a new version of VA).
Another option is to switch from .txt file defined properties to property sheets that can be inherited by multiple projects. VA doesn't parse the project files but relies on the VcProjectEngine. It does appear to evaluate property sheets and I would have expected that compiler response files would work too.
When case=718 was originally opened, VA did parse the project file, but we've since switched to using the VcProjectEngine COM object.
You might want to generate a VA log and send it in. We'll be able to see if the additional include directories are getting to VA or not.
Parsing .txt files from cproj "additional options"
Posted - Apr 28 2010 : 4:15:31 PM
