Commit: 9eaf7d503afc8232391067fa20528bc24bd98bf4 Author: Christoph M. Becker <[email protected]> Tue, 4 Jun 2019 17:23:05 +0200 Parents: 5c54f2f83d233279d5f7b1400be022dccbd6bfa9 Branches: master
Link: http://git.php.net/?p=web/windows.git;a=commitdiff;h=9eaf7d503afc8232391067fa20528bc24bd98bf4 Log: Explain naming change from vc15 to vs16 Changed paths: M docroot/index.php Diff: diff --git a/docroot/index.php b/docroot/index.php index 625f675..2a862fe 100644 --- a/docroot/index.php +++ b/docroot/index.php @@ -30,6 +30,24 @@ include TPL_PATH . 'news_line.php'; <div class="content"> <div class="block"> <!-- .block --> + <div class="info entry"> + <!-- .info --> + <h3 class="summary entry-title">Visual Studio 2019 Builds</h3> + <?php news_date('04-Jun-2019') ?> + <div> + <p>All binary packages we were offering contained "vc#" (for instance, "vc14") in the filename to designate + the Visual Studio version which has been used to build them. This number ("#") has tradionally been + the major number of the respective platform toolset. The preview releases of Visual Studio 2017 shipped + with platform toolset 15.00, so we used "vc15" to mark the files. The first GA release of Visual Studio + 2017, however, shipped with platform toolset 14.10 (to signal the backward compatibility), but the + internal Visual Studio version number stayed 15.00. To avoid confusion with already distributed packages, + we stuck with the "vc15" marker. For our Visual Studio 2019 builds (PHP 7.4 and master) we finally changed + from "vc#" to "vs#" (note the "s"), where the number now designates the major internal Visual Studio + version number. We are planning to stick with this new naming scheme for the foreseeable future. + </p> + </div> + </div><!-- .info --> + <div class="info entry"> <!-- .info --> <h3 class="summary entry-title">OpenSSL 1.1.1a</h3> -- PHP Webmaster List Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
