I think I found the answer, however incomplete.
You can specify something like this in the properties:
<PropertyGroup> <ProjectIncludeDir>@(ClCompile->'%(AdditionalIncludeDirectories)')</ProjectIncludeDir> </PropertyGroup>
This will cause the $ (ProjectIncludeDir) macro to be available for custom build steps that also contain a list of included directories.
The problem with this approach is that string operations on this macro are no longer possible. For example, consider the following:
<ProjectIncludeDirDot>$(ProjectIncludeDir.Replace(';',','))</ProjectIncludeDirDot>
This is the result of the macro $ (ProjectIncludeDirDot) at @ (ClCompile â '% (AdditionalIncludeDirectories)'). It seems that the transforms are calculated after a macro evaluation, which violates this replacement. If someone knows for a better solution, please ...
source share