The "macros" available in the property settings are actually environment variables added by Visual Studio. If you set the environment variable in your user profile, you can add it to your property sheet in the same way as you use the "built-in" VS macros.
For example, I have a network hard drive with a folder named LIBS containing Boost, Google Test, Google Mock, Tiny XML, and several dozen other libraries. I mount it as the drive letter Z , and I have an environment variable set in my user profile named XTPLIBRARIES that points to Z:\LIBS . In my properties page, I have configured inclusion paths as shown below.
$ (XTPLIBRARIES) \ boost_1_53_0 \ boost
$ (XTPLIBRARIES) \ GTEST-1.6.0 \ include
$ (XTPLIBRARIES) \ tinyxml2
Now, when I create a new project, I just add a property sheet, and everything works as expected, until the environment variable is set, of course.
Captain obvlious
source share