A new SCons checkpoint release, 2.0.1.beta.20100627, is now available
on the SCons download page:
The primary purpose of this release is to remove support for Python
versions prior to 2.4 and streamline the SCons code base using more
modern python idioms.
IMPORTANT: In 1.3.0 and 2.0.0, explicit dependencies (configured via
the Depends() call) are ignored for any nodes that do not have builders.
This known issue will typically only happen if you explicitly
configure a builder call to create multiple output files, some of which
are "hidden" from SCons by not being listed in the targets list, and then
use Depends() to establish an explicit dependency on a "hidden" file.
 See http://scons.tigris.org/issues/show_bug.cgi?id=2647 for details.
A SCons "checkpoint release" is intended to provide early access to
new features so they can be tested in the field before being released
for adoption by other software distributions.
Note that a checkpoint release is developed using the same test-driven
development methodology as all SCons releases. Existing SCons
functionality should all work as it does in previous releases (except
for any changes identified in the release notes) and early adopters
should be able to use a checkpoint release safely for production work
with existing SConscript files. If not, it represents not only a bug
in SCons but also a hole in the regression test suite, and we want to
hear about it.
New features may be more lightly tested than in past releases,
especially as concerns their interaction with all of the other
functionality in SCons. We are especially interested in hearing bug
reports about new functionality.
We do not recommend that downstream distributions (Debian, Fedora,
etc.) package a checkpoint release, mainly to avoid confusing the
"public" release numbering with the long checkpoint release names.
Here is a summary of the changes since 1.3:
All features or usages deprecated in 1.3 should have been removed.
Uses of formerly-deprecated features should get an error.
The BuildDir() method and the build_dir option now get warnings.
The SourceCode() function and its associated factory functions have
started their deprecation cycle and can have a warning enabled.
CHANGED/ENHANCED EXISTING FUNCTIONALITY
Any Command() or env.Command() calls that use the following Action
factory functions will have their targets rebuilt when upgrading
from any pre-2.0 release:
Chmod() Copy() Delete() Mkdir() Move() Touch()
(The rebuild occurs because the underlying Python class that
implements these functions has been changed to a new-style Python
class, and that changes the Python byte code and therefore the
build signature of the functions.)
MSVC/MSVS/SDK support has been improved. A number of issues with
determining the correct version and architecture have been resolved.
Fix propagation from environment of VS*COMNTOOLS to resolve issues
initializing MSVC/MSVS/SDK issues.
Fixed a case-sensitivity problem with Fortran modules.
Fix the ability to append to default $*FLAGS values (which are
implemented as CLVar instances) in a copied construction environment
without affecting the original construction environment's value.
Updated the TeX command strings to include a /D on Windows in
case the new directory is on a different drive letter.
Fixed the LaTeX scanner so dependencies are found in commands that
are broken across lines with a comment or have embedded spaces.
The entries for SourceCode() and its associated factory functions now
state that the functions are deprecated.
Document the AllowSubstExceptions() function in the User's Guide.
Thanks to Greg Noel, Steven Knight, Dirk Baechle, William Deegan,
W. Trevor King, Joe Zuntz, Bauke Conijn, Matt Hughes, Rob Managan, and Jim Randall
for their contributions to this release.
Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 The SCons Foundation
src/RELEASE.txt 5023 2010/06/14 22:05:46 scons
Log in to post a comment.