Re: [Scons-dev] SCons 2.4.0 Released
> On Sep 23, 2015, at 11:32 , Dirk Bächle wrote: > > Hi all, > > On 23.09.2015 12:28, Russel Winder wrote: >> On Tue, 2015-09-22 at 09:13 +0200, Dirk Bächle wrote: >>> >> […] >>> >>> I volunteer to weed out some of the old Python 2.x stuff (where x < 7 >>> ;) ) on a separate bug branch. I have all the scons_testsuite >>> stuff ready (just like for the slots change), in order to show that >>> there are no large speed penalties coming with it. >>> >>> >> Does this mean we can revert all the 2.6-isms that were introduced >> instead of using nice 2.7, 3.3+-isms? >> > > > I'd suggest to continue as follows: > > - Remove special Python constructs for Python 2.5 and smaller on a bug > branch, then merge it >to tip of "default" as usual. > - I'd then like to add another issue on top of this where I do some changes > to the core architecture >(pushing classes around to entangle the dependencies of Node and > Taskmaster a little bit), again >merged to "default". > - Then, merge this new tip of "default" to the "python3" branch. > - Continue with bugfixing on "default", while on "python3" we can then start > to remove 2.6 constructs >and work on getting the code to be 2.7/3.x compatible at the same time. > Has anyone tried to run futurize with the “-1” option? It’s specifically designed to modify 2.x code to the 2.7 compatibility standard without requiring any external code (does not need to “import future” but does add “from __future__…”). It specifically does not try for python 3 support in that mode. — Tim Jenness ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons 2.4.0 Released
Hi all, On 23.09.2015 12:28, Russel Winder wrote: On Tue, 2015-09-22 at 09:13 +0200, Dirk Bächle wrote: […] I volunteer to weed out some of the old Python 2.x stuff (where x < 7 ;) ) on a separate bug branch. I have all the scons_testsuite stuff ready (just like for the slots change), in order to show that there are no large speed penalties coming with it. Does this mean we can revert all the 2.6-isms that were introduced instead of using nice 2.7, 3.3+-isms? I'd suggest to continue as follows: - Remove special Python constructs for Python 2.5 and smaller on a bug branch, then merge it to tip of "default" as usual. - I'd then like to add another issue on top of this where I do some changes to the core architecture (pushing classes around to entangle the dependencies of Node and Taskmaster a little bit), again merged to "default". - Then, merge this new tip of "default" to the "python3" branch. - Continue with bugfixing on "default", while on "python3" we can then start to remove 2.6 constructs and work on getting the code to be 2.7/3.x compatible at the same time. Best regards, Dirk ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons 2.4.0 Released
On Mon, 2015-09-21 at 21:13 -0700, Tim Jenness wrote: > > […] > > As a scons user I’d much prefer a minor slow down coming from the > refactor if it gave me a python 3 version. Agreed. I am trying to expunge all Python 2 from all my systems. However the current state of the SCons Python 3 branch isn't really up to usage. I guess there now needs to be another merge of tip into the Python 3 branch and deal with the fall out. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons 2.4.0 Released
On Tue, 2015-09-22 at 09:13 +0200, Dirk Bächle wrote: > […] > > I volunteer to weed out some of the old Python 2.x stuff (where x < 7 > ;) ) on a separate bug branch. I have all the scons_testsuite > stuff ready (just like for the slots change), in order to show that > there are no large speed penalties coming with it. > > Does this mean we can revert all the 2.6-isms that were introduced instead of using nice 2.7, 3.3+-isms? -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons 2.4.0 Released
Next thing is to merge default into the python3 branch. I did this a few months ago; you can look at the merge to see the kinds of things that have to be tweaked, it's not usually too bad. On Tue, Sep 22, 2015 at 3:44 PM, Tim Jenness wrote: > > > On Sep 22, 2015, at 12:33 , Bill Deegan > wrote: > > > > Tim, > > > > Feel free to help out on the python 3 work then. > > > > Ok. Where do I start? (I’m trying to get a buildbot slave set up but the > process of locating a linux machine is taking a while). > > Last time I looked the Python3 branch was a year old. Are we starting from > current master? Are we committed to six or is future an option (I use > future in my own projects). > > — > Tim Jenness > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > -- Gary ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons 2.4.0 Released
> On Sep 22, 2015, at 12:33 , Bill Deegan wrote: > > Tim, > > Feel free to help out on the python 3 work then. > Ok. Where do I start? (I’m trying to get a buildbot slave set up but the process of locating a linux machine is taking a while). Last time I looked the Python3 branch was a year old. Are we starting from current master? Are we committed to six or is future an option (I use future in my own projects). — Tim Jenness ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons 2.4.0 Released
Tim, Feel free to help out on the python 3 work then. -Bill On Mon, Sep 21, 2015 at 9:13 PM, Tim Jenness wrote: > > > On Sep 21, 2015, at 20:09 , Bill Deegan > wrote: > > > > William, > > > > Sounds good. > > I'd like to make sure we get some performance profiling before/after > such changes to make sure we don't slow SCons down. > > > > As a scons user I’d much prefer a minor slow down coming from the refactor > if it gave me a python 3 version. > > — > Tim Jenness > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons 2.4.0 Released
Sounds good. I have used that suite before. I will have to set it back up on this machine. I may have some questions about required tools. Not sure if I could get all 3 profiler steps working. V/R, William On Tue, Sep 22, 2015 at 8:13 AM, Dirk Bächle wrote: > Hi there, > > On 22.09.2015 05:09, Bill Deegan wrote: > >> William, >> >> Sounds good. >> I'd like to make sure we get some performance profiling before/after such >> changes to make sure we don't slow SCons down. >> >> > I volunteer to weed out some of the old Python 2.x stuff (where x < 7 ;) ) > on a separate bug branch. I have all the scons_testsuite stuff ready (just > like for the slots change), in order to show that there are no large speed > penalties coming with it. > > Best regards, > > Dirk > > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons 2.4.0 Released
Hi there, On 22.09.2015 05:09, Bill Deegan wrote: William, Sounds good. I'd like to make sure we get some performance profiling before/after such changes to make sure we don't slow SCons down. I volunteer to weed out some of the old Python 2.x stuff (where x < 7 ;) ) on a separate bug branch. I have all the scons_testsuite stuff ready (just like for the slots change), in order to show that there are no large speed penalties coming with it. Best regards, Dirk ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons 2.4.0 Released
> On Sep 21, 2015, at 20:09 , Bill Deegan wrote: > > William, > > Sounds good. > I'd like to make sure we get some performance profiling before/after such > changes to make sure we don't slow SCons down. > As a scons user I’d much prefer a minor slow down coming from the refactor if it gave me a python 3 version. — Tim Jenness ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons 2.4.0 Released
Since we are officially done with versions of python prior to 2.7.X, would anyone be opposed to refactor work to get rid of some legacy code? I am sure we are all aware of code that can be simplified or removed for newer standard library calls. On Tue, Sep 22, 2015 at 1:06 AM, William Blevins wrote: > Never mind. I am apparently illiterate. I think I need more rest or > something. > > Thanks for the hard work! > > On Tue, Sep 22, 2015 at 1:02 AM, William Blevins > wrote: > >> Looks like some of the docs refer to 2.3.6 rather than 2.4.0. I wouldn't >> release over it, but it might be something to fix for the next release(s). >> >> Can we do an announcement for CL support? >> >> V/R, >> William >> >> On Mon, Sep 21, 2015 at 7:18 PM, Bill Deegan >> wrote: >> >>> >>> >>>SCons - a software construction tool >>> >>> Release Notes >>> >>> >>> This is SCons, a tool for building software (and other files). SCons is >>> implemented in Python, and its "configuration files" are actually Python >>> scripts, allowing you to use the full power of a real scripting language >>> to solve build problems. You do not, however, need to know Python to >>> use SCons effectively. >>> >>> Please go to http://www.scons.org/download.php to get the latest >>> production >>> release of SCons. >>> >>> So that everyone using SCons can help each other learn how to use it more >>> effectively, please go to http://scons.org/lists.php#users to sign up >>> for >>> the scons-users mailing list. >>> >>> ==IMPORTANT NOTICE=== >>> >>> As has been pre-announced in SCons's mailing lists: >>> >>> * https://pairlist4.pair.net/pipermail/scons-users/2014-July/002734.html >>> , >>> * >>> https://pairlist2.pair.net/pipermail/scons-dev/2014-December/002107.html >>> * >>> https://pairlist4.pair.net/pipermail/scons-users/2015-February/003454.html >>> >>> We're planning to switch the Node class to using "slots" in the core >>> sources, >>> mainly to reduce memory consumption by up to 35% in large build projects. >>> >>> This feature has been tested extensively and we don't expect any >>> problems for you. >>> However as with all major changes it would be wise to test V2.4.0 when >>> it is >>> released. Especially if you are directly using the Node class. >>> >>> = >>> >>> >>> RELEASE 2.4.0 - Mon, 21 Sep 2015 09:07:51 -0700 >>> >>> Please consult the RELEASE.txt file for a summary of changes since the >>> last >>> release and consult the CHANGES.txt file for complete a list of changes >>> since last release. This announcement highlights only the important >>> changes. >>> >>> Please note the following important changes since release 2.3.6: >>> - Switch several core classes to use "slots" to reduce memory >>> usage. (PR #2180, #2178, #2198) >>> >>> Please note the following important changes since release 2.3.5: >>> - Support for Visual Studio 2015 >>> >>> Please note the following important changes since release 2.3.4: >>> - Documentation fixes for libraries.xml and >>> builders-writing.xml (#2989 and #2990) >>> - Extended docs for InstallVersionedLib/SharedLibrary, >>> and added SKIP_WIN_PACKAGES argument to build script >>> bootstrap.py (PR #230, #3002). >>> - Fixed symlink support (PR #227, #2395). >>> - Updated debug-count test case (PR #229). >>> - Fixed incomplete LIBS flattening and substitution in >>> Program scanner(PR #205, #2954). >>> - Added new method rentry_exists_on_disk to Node.FS (PR #193). >>> - Fixed several D tests under the different OS. >>> - Add support for f08 file extensions for Fortran 2008 code. >>> - Show --config choices if no argument is specified (PR #202). >>> - Fixed build crash when XML toolchain isn't installed, and >>> activated compression for ZIP archives. >>> - Fix for VersionedSharedLibrary under 'sunos' platform. >>> - Fixed dll link with precompiled headers on MSVC 2012 >>> - Added an 'exclude' parameter to Glob() >>> - Support for multiple cmdargs (one per variant) in VS project files. >>> - Various improvements for TempFileMunge class. >>> - Added an implementation for Visual Studio users files (PR #209). >>> - Added support for the 'PlatformToolset' tag in VS project files >>> (#2978). >>> - Added support for '-isystem' to ParseFlags. >>> >>> >>> Please note the following important changes since release 2.3.3: >>> >>> -- Fix for EnsureSConsVersion regression in 2.3.3. >>> >>> -- Fix for interactive mode with Configure contexts >>> >>> Please note the following important changes since release 2.3.2: >>> >>> -- On Windows, .def files did not work as sources to shared >>>libraries or executables, due to a regression which is >>>corrected in 2.3.3. >>> >>> Please note the following important changes since release 2.
Re: [Scons-dev] SCons 2.4.0 Released
Never mind. I am apparently illiterate. I think I need more rest or something. Thanks for the hard work! On Tue, Sep 22, 2015 at 1:02 AM, William Blevins wrote: > Looks like some of the docs refer to 2.3.6 rather than 2.4.0. I wouldn't > release over it, but it might be something to fix for the next release(s). > > Can we do an announcement for CL support? > > V/R, > William > > On Mon, Sep 21, 2015 at 7:18 PM, Bill Deegan > wrote: > >> >> >>SCons - a software construction tool >> >> Release Notes >> >> >> This is SCons, a tool for building software (and other files). SCons is >> implemented in Python, and its "configuration files" are actually Python >> scripts, allowing you to use the full power of a real scripting language >> to solve build problems. You do not, however, need to know Python to >> use SCons effectively. >> >> Please go to http://www.scons.org/download.php to get the latest >> production >> release of SCons. >> >> So that everyone using SCons can help each other learn how to use it more >> effectively, please go to http://scons.org/lists.php#users to sign up for >> the scons-users mailing list. >> >> ==IMPORTANT NOTICE=== >> >> As has been pre-announced in SCons's mailing lists: >> >> * https://pairlist4.pair.net/pipermail/scons-users/2014-July/002734.html >> , >> * >> https://pairlist2.pair.net/pipermail/scons-dev/2014-December/002107.html >> * >> https://pairlist4.pair.net/pipermail/scons-users/2015-February/003454.html >> >> We're planning to switch the Node class to using "slots" in the core >> sources, >> mainly to reduce memory consumption by up to 35% in large build projects. >> >> This feature has been tested extensively and we don't expect any problems >> for you. >> However as with all major changes it would be wise to test V2.4.0 when it >> is >> released. Especially if you are directly using the Node class. >> >> = >> >> >> RELEASE 2.4.0 - Mon, 21 Sep 2015 09:07:51 -0700 >> >> Please consult the RELEASE.txt file for a summary of changes since the >> last >> release and consult the CHANGES.txt file for complete a list of changes >> since last release. This announcement highlights only the important >> changes. >> >> Please note the following important changes since release 2.3.6: >> - Switch several core classes to use "slots" to reduce memory >> usage. (PR #2180, #2178, #2198) >> >> Please note the following important changes since release 2.3.5: >> - Support for Visual Studio 2015 >> >> Please note the following important changes since release 2.3.4: >> - Documentation fixes for libraries.xml and >> builders-writing.xml (#2989 and #2990) >> - Extended docs for InstallVersionedLib/SharedLibrary, >> and added SKIP_WIN_PACKAGES argument to build script >> bootstrap.py (PR #230, #3002). >> - Fixed symlink support (PR #227, #2395). >> - Updated debug-count test case (PR #229). >> - Fixed incomplete LIBS flattening and substitution in >> Program scanner(PR #205, #2954). >> - Added new method rentry_exists_on_disk to Node.FS (PR #193). >> - Fixed several D tests under the different OS. >> - Add support for f08 file extensions for Fortran 2008 code. >> - Show --config choices if no argument is specified (PR #202). >> - Fixed build crash when XML toolchain isn't installed, and >> activated compression for ZIP archives. >> - Fix for VersionedSharedLibrary under 'sunos' platform. >> - Fixed dll link with precompiled headers on MSVC 2012 >> - Added an 'exclude' parameter to Glob() >> - Support for multiple cmdargs (one per variant) in VS project files. >> - Various improvements for TempFileMunge class. >> - Added an implementation for Visual Studio users files (PR #209). >> - Added support for the 'PlatformToolset' tag in VS project files >> (#2978). >> - Added support for '-isystem' to ParseFlags. >> >> >> Please note the following important changes since release 2.3.3: >> >> -- Fix for EnsureSConsVersion regression in 2.3.3. >> >> -- Fix for interactive mode with Configure contexts >> >> Please note the following important changes since release 2.3.2: >> >> -- On Windows, .def files did not work as sources to shared >>libraries or executables, due to a regression which is >>corrected in 2.3.3. >> >> Please note the following important changes since release 2.3.0: >> >> -- BitKeeper, CVS, Perforce, RCS, SCCS are deprecated from the >>default toolset and will be removed from the default toolset >>in future SCons versions to speed up SCons initialization. >>The tools themselves continue to be supported. >> >> -- Support for Visual Studio 12.0Exp and 2013 >> >> -- Revamp of D language support, focusing on D v2. >>D v1 is now deprecated. >> >>
Re: [Scons-dev] SCons 2.4.0 Released
Looks like some of the docs refer to 2.3.6 rather than 2.4.0. I wouldn't release over it, but it might be something to fix for the next release(s). Can we do an announcement for CL support? V/R, William On Mon, Sep 21, 2015 at 7:18 PM, Bill Deegan wrote: > > >SCons - a software construction tool > > Release Notes > > > This is SCons, a tool for building software (and other files). SCons is > implemented in Python, and its "configuration files" are actually Python > scripts, allowing you to use the full power of a real scripting language > to solve build problems. You do not, however, need to know Python to > use SCons effectively. > > Please go to http://www.scons.org/download.php to get the latest > production > release of SCons. > > So that everyone using SCons can help each other learn how to use it more > effectively, please go to http://scons.org/lists.php#users to sign up for > the scons-users mailing list. > > ==IMPORTANT NOTICE=== > > As has been pre-announced in SCons's mailing lists: > > * https://pairlist4.pair.net/pipermail/scons-users/2014-July/002734.html , > * https://pairlist2.pair.net/pipermail/scons-dev/2014-December/002107.html > * > https://pairlist4.pair.net/pipermail/scons-users/2015-February/003454.html > > We're planning to switch the Node class to using "slots" in the core > sources, > mainly to reduce memory consumption by up to 35% in large build projects. > > This feature has been tested extensively and we don't expect any problems > for you. > However as with all major changes it would be wise to test V2.4.0 when it > is > released. Especially if you are directly using the Node class. > > = > > > RELEASE 2.4.0 - Mon, 21 Sep 2015 09:07:51 -0700 > > Please consult the RELEASE.txt file for a summary of changes since the > last > release and consult the CHANGES.txt file for complete a list of changes > since last release. This announcement highlights only the important > changes. > > Please note the following important changes since release 2.3.6: > - Switch several core classes to use "slots" to reduce memory > usage. (PR #2180, #2178, #2198) > > Please note the following important changes since release 2.3.5: > - Support for Visual Studio 2015 > > Please note the following important changes since release 2.3.4: > - Documentation fixes for libraries.xml and > builders-writing.xml (#2989 and #2990) > - Extended docs for InstallVersionedLib/SharedLibrary, > and added SKIP_WIN_PACKAGES argument to build script > bootstrap.py (PR #230, #3002). > - Fixed symlink support (PR #227, #2395). > - Updated debug-count test case (PR #229). > - Fixed incomplete LIBS flattening and substitution in > Program scanner(PR #205, #2954). > - Added new method rentry_exists_on_disk to Node.FS (PR #193). > - Fixed several D tests under the different OS. > - Add support for f08 file extensions for Fortran 2008 code. > - Show --config choices if no argument is specified (PR #202). > - Fixed build crash when XML toolchain isn't installed, and > activated compression for ZIP archives. > - Fix for VersionedSharedLibrary under 'sunos' platform. > - Fixed dll link with precompiled headers on MSVC 2012 > - Added an 'exclude' parameter to Glob() > - Support for multiple cmdargs (one per variant) in VS project files. > - Various improvements for TempFileMunge class. > - Added an implementation for Visual Studio users files (PR #209). > - Added support for the 'PlatformToolset' tag in VS project files > (#2978). > - Added support for '-isystem' to ParseFlags. > > > Please note the following important changes since release 2.3.3: > > -- Fix for EnsureSConsVersion regression in 2.3.3. > > -- Fix for interactive mode with Configure contexts > > Please note the following important changes since release 2.3.2: > > -- On Windows, .def files did not work as sources to shared >libraries or executables, due to a regression which is >corrected in 2.3.3. > > Please note the following important changes since release 2.3.0: > > -- BitKeeper, CVS, Perforce, RCS, SCCS are deprecated from the >default toolset and will be removed from the default toolset >in future SCons versions to speed up SCons initialization. >The tools themselves continue to be supported. > > -- Support for Visual Studio 12.0Exp and 2013 > > -- Revamp of D language support, focusing on D v2. >D v1 is now deprecated. > > -- Fixed NoClean() for multi-target builders. > > -- RPM and m4 are no longer in the default toolset on Windows. >Should improve startup speed. > > -- TeX fixes: -synctex=1 and cleaning auxiliary files. > > -- Fixes to the Docbook tool. > > Please note the following importan
[Scons-dev] SCons 2.4.0 Released
SCons - a software construction tool Release Notes This is SCons, a tool for building software (and other files). SCons is implemented in Python, and its "configuration files" are actually Python scripts, allowing you to use the full power of a real scripting language to solve build problems. You do not, however, need to know Python to use SCons effectively. Please go to http://www.scons.org/download.php to get the latest production release of SCons. So that everyone using SCons can help each other learn how to use it more effectively, please go to http://scons.org/lists.php#users to sign up for the scons-users mailing list. ==IMPORTANT NOTICE=== As has been pre-announced in SCons's mailing lists: * https://pairlist4.pair.net/pipermail/scons-users/2014-July/002734.html , * https://pairlist2.pair.net/pipermail/scons-dev/2014-December/002107.html * https://pairlist4.pair.net/pipermail/scons-users/2015-February/003454.html We're planning to switch the Node class to using "slots" in the core sources, mainly to reduce memory consumption by up to 35% in large build projects. This feature has been tested extensively and we don't expect any problems for you. However as with all major changes it would be wise to test V2.4.0 when it is released. Especially if you are directly using the Node class. = RELEASE 2.4.0 - Mon, 21 Sep 2015 09:07:51 -0700 Please consult the RELEASE.txt file for a summary of changes since the last release and consult the CHANGES.txt file for complete a list of changes since last release. This announcement highlights only the important changes. Please note the following important changes since release 2.3.6: - Switch several core classes to use "slots" to reduce memory usage. (PR #2180, #2178, #2198) Please note the following important changes since release 2.3.5: - Support for Visual Studio 2015 Please note the following important changes since release 2.3.4: - Documentation fixes for libraries.xml and builders-writing.xml (#2989 and #2990) - Extended docs for InstallVersionedLib/SharedLibrary, and added SKIP_WIN_PACKAGES argument to build script bootstrap.py (PR #230, #3002). - Fixed symlink support (PR #227, #2395). - Updated debug-count test case (PR #229). - Fixed incomplete LIBS flattening and substitution in Program scanner(PR #205, #2954). - Added new method rentry_exists_on_disk to Node.FS (PR #193). - Fixed several D tests under the different OS. - Add support for f08 file extensions for Fortran 2008 code. - Show --config choices if no argument is specified (PR #202). - Fixed build crash when XML toolchain isn't installed, and activated compression for ZIP archives. - Fix for VersionedSharedLibrary under 'sunos' platform. - Fixed dll link with precompiled headers on MSVC 2012 - Added an 'exclude' parameter to Glob() - Support for multiple cmdargs (one per variant) in VS project files. - Various improvements for TempFileMunge class. - Added an implementation for Visual Studio users files (PR #209). - Added support for the 'PlatformToolset' tag in VS project files (#2978). - Added support for '-isystem' to ParseFlags. Please note the following important changes since release 2.3.3: -- Fix for EnsureSConsVersion regression in 2.3.3. -- Fix for interactive mode with Configure contexts Please note the following important changes since release 2.3.2: -- On Windows, .def files did not work as sources to shared libraries or executables, due to a regression which is corrected in 2.3.3. Please note the following important changes since release 2.3.0: -- BitKeeper, CVS, Perforce, RCS, SCCS are deprecated from the default toolset and will be removed from the default toolset in future SCons versions to speed up SCons initialization. The tools themselves continue to be supported. -- Support for Visual Studio 12.0Exp and 2013 -- Revamp of D language support, focusing on D v2. D v1 is now deprecated. -- Fixed NoClean() for multi-target builders. -- RPM and m4 are no longer in the default toolset on Windows. Should improve startup speed. -- TeX fixes: -synctex=1 and cleaning auxiliary files. -- Fixes to the Docbook tool. Please note the following important changes since release 2.3.0: -- Fix failure to relink when LINKCOM or libs change, introduced in 2.3.0. -- Fix MSVC defaulting TARGET_ARCH to HOST_ARCH and other MSVC issues. -- Reduced memory consumption in large builds, which should speed them up as well. -- Add new cyglink linker for use with cygwin. -- Fix leaking file handles to subprocesses -- Support read-only cache (--cache-readonly) -- Add Pseudo
