summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohnny Willemsen <jwillemsen@remedy.nl>2017-04-12 17:19:33 +0200
committerJohnny Willemsen <jwillemsen@remedy.nl>2017-04-12 17:19:33 +0200
commitb8ec91dc97a149f68b4c0bd1b7fa7930e5a86c25 (patch)
tree38359d10926e10456dd44ef476c738c17fe49cba
parent83bd2e711d2ae5a7b20c209f5a93ca6179985e94 (diff)
downloadMPC-b8ec91dc97a149f68b4c0bd1b7fa7930e5a86c25.tar.gz
vc15 is now vs2017
* docs/html/MakeProjectCreator.html:
-rw-r--r--docs/html/MakeProjectCreator.html12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/html/MakeProjectCreator.html b/docs/html/MakeProjectCreator.html
index b82bbd9b..0806e26a 100644
--- a/docs/html/MakeProjectCreator.html
+++ b/docs/html/MakeProjectCreator.html
@@ -1826,7 +1826,7 @@ class="XRef">the -workers_port option</a>,
"Code">vc7</em>, <em class="Code">vc71</em>, <em class="Code">vc8</em>,
<em class="Code">vc9</em>, <em class="Code">vc10</em>, <em class="Code">vc11</em>,
<em class="Code">vc12</em>, <em class="Code">vc14</em> and
- <em class="Code">vc15</em> project types. If this environment
+ <em class="Code">vs2017</em> project types. If this environment
variable is set, MPC will generate inter-project dependencies for
libraries within a single workspace. This is usually not desired
since adding these dependencies in a static workspace has the side
@@ -1982,7 +1982,7 @@ class="XRef">the -workers_port option</a>,
<p class="Code">
&nbsp;&nbsp;exclude(vc6, vc7, vc71, vc8, vc9,
- vc10, vc11, vc12, vc14, vc15, nmake) {
+ vc10, vc11, vc12, vc14, vs2017, nmake) {
</p>
<p class="Code">&nbsp;&nbsp;&nbsp;&nbsp;this_directory</p>
@@ -2590,7 +2590,7 @@ class="Code">specific</em> clause.
<em class="Code">vc8</em>, <em class="Code">vc9</em>,
<em class="Code">vc10</em>, <em class="Code">vc11</em>,
<em class="Code">vc12</em>, <em class="Code">vc14</em>,
- and <em class="Code">vc15</em> project types.
+ and <em class="Code">vs2017</em> project types.
</p>
</td>
</tr>
@@ -3237,7 +3237,7 @@ class="Code">specific</em> clause.
"Code">vc7</em>, <em class="Code">vc71</em>, <em class="Code">vc8</em>,
<em class="Code">vc9</em>, <em class="Code">vc10</em>, <em class="Code">vc11</em>,
<em class="Code">vc12</em>, <em class="Code">vc14</em>, and
- <em class="Code">vc15</em> project types.
+ <em class="Code">vs2017</em> project types.
</p>
<p class="Body">
@@ -8097,7 +8097,7 @@ class="Code">specific</em> clause.
7.10 is return for vc71 and 8.00 is returned for vc8,
9.00 is returned for vc9, 10.00 is returned for vc10,
11.00 is returned for vc11, 12.0 is returned for vc12,
- 14.0 is returned for vc14, 15.0 is returned for vc15.
+ 14.0 is returned for vc14, 14.1 is returned for vs2017.
</p>
</td>
</tr>
@@ -8415,7 +8415,7 @@ class="Code">specific</em> clause.
<p class="Body">
Certain project types don't support the same
input file used by multiple custom types (current examples of
- this are vc10, vc11, vc12, vc14, vc15, cdt6, and cdt7). To accomodate these types, MPC
+ this are vc10, vc11, vc12, vc14, vs2017, cdt6, and cdt7). To accommodate these types, MPC
has a capability called "combined custom". With this capability
enabled in the specific ProjectCreator, MPC will "fold together"
the multiple custom steps so that the target tool (Visual Studio