Commits

Anonymous committed aef1cd0

Prepare for release.

Comments (0)

Files changed (7)

HOWTO/release.txt

 IMPORTANT:  Release 0.11 contains the following interface changes:
   - XXX
 
+  See the release notes for more information about these changes.
+
 This release adds the following features:
   - XXX
 
 You may, of course, override these default values by appropriate
 configuration of Environment construction variables.
 
+By default, SCons knows how to search for available programming tools
+on various systems--see the SCons man page for details.  You may,
+of course, override the default SCons choices made by appropriate
+configuration of Environment construction variables.
+
 
 INSTALLATION REQUIREMENTS
 =========================
 Python 1.5.2, you may not have distutils installed.  If you are running
 Python version 1.6 or later, you should be fine.
 
-NOTE TO RED HAT USERS:  All Red Hat Linux versions as late as 7.3 (at
-least) still ship Python 1.5.2 as the default, so you probably do *not*
-have distutils installed, unless you have already done so manually.
+NOTE TO RED HAT USERS:  All Red Hat Linux versions up to 7.3 still ship
+Python 1.5.2 as the default, so you probably do *not* have distutils
+installed, unless you have already done so manually or are running Red
+Hat 8.0 or later.
 
 In this case, your options are:
 
 
         $ scons build/scons
 
-If you don't have SCons version 0.08 or later already installed on your
+If you don't have SCons version 0.11 or later already installed on your
 system, you can use SCons itself to populate the build/scons/ directory
 with a little more typing:
 
 BUILDING PACKAGES
 =================
 
-We now use SCons (version 0.08 or later) to build its own packages.
+We now use SCons (version 0.11 or later) to build its own packages.
 If you already have an appropriate version of SCons installed on your
 system, you can build everything by simply running it:
 
         $ scons
 
-If you don't have SCons version 0.08 or later already installed on your
+If you don't have SCons version 0.11 or later already installed on your
 system, you can build this version of SCons with itself with a little
 more typing:
 
 
   * Fifth post-official-Debian build cycle
 
- -- Steven Knight <knight@baldmt.com>  Thu, 16 Jan 2003 04:11:46 -0600
-
+ -- Steven Knight <knight@baldmt.com>  Tue, 11 Feb 2003 05:24:33 -0600
 
 scons (0.10-1) unstable; urgency=low
 
 the GCC tool chain,
 and the Microsoft Visual C++ tools,
 On SGI IRIX systems,
-.B
+.B scons
 searches for the MIPSPro compiler tools
 and the GCC tool chain.
 And on all other platforms,
 
 
 
-RELEASE 0.11 - XXX
+RELEASE 0.11 - Tue, 11 Feb 2003 05:24:33 -0600
 
   From Chad Austin:
 
 
   From Anthony Roach:
 
-  - Use a different static object suffix (.os) when using gcc so shared
+  - Use a different shared object suffix (.os) when using gcc so shared
     and static objects can exist side-by-side in the same directory.
 
   - Allow the same object files on Win32 to be linked into either
 an additional requirement to *install* SCons from this particular
 package; see the next section.)
 
-The default SCons configuration assumes use of the Microsoft Visual C++
-compiler suite on WIN32 systems, and assumes a C compiler named 'cc',
-a C++ compiler named 'c++', and a Fortran compiler named 'g77' (such
-as found in the GNU C compiler suite) on any other type of system.
-You may, of course, override these default values by appropriate
+By default, SCons knows how to search for available programming tools
+on various systems--see the SCons man page for details.  You may,
+of course, override the default SCons choices made by appropriate
 configuration of Environment construction variables.
 
 
 1.5.2, you may not have distutils installed.  If you are running
 Python version 1.6 or later, you should be fine.
 
-NOTE TO RED HAT USERS:  All Red Hat Linux versions as late as 7.3
-still ship Python 1.5.2 as the default, so you probably do *not* have
-distutils installed, unless you have already done so manually.
+NOTE TO RED HAT USERS:  All Red Hat Linux versions up to 7.3 still ship
+Python 1.5.2 as the default, so you probably do *not* have distutils
+installed, unless you have already done so manually or are running Red
+Hat 8.0 or later.
 
 In this case, your options are:
 
 
 
 
-RELEASE 0.10 - Thu, 16 Jan 2003 04:11:46 -0600
+RELEASE 0.11 - Tue, 11 Feb 2003 05:24:33 -0600
 
-  This is the tenth alpha release of SCons.  Please consult the
+  This is the eleventh alpha release of SCons.  Please consult the
   CHANGES.txt file for a list of specific changes since last release.
 
   Please note the following important changes since release 0.10:
 
-    - The default suffix for shared object files when using gcc has now
-      been changed to '.os'.  This makes library builds more convenient
-      by allowing both static (compiled without -fPIC) and shared object
-      files (compiled with -fPIC) to exist side-by-side.  If you want to
-      preserve the old behavior of using .o files for shared objects,
-      you must now explicitly reset the SHOBJSUFFIX value in your
-      construction environment as follows:
+    - The default suffix for shared object files when using gcc has
+      now been changed to '.os'.  This is to make library builds more
+      convenient by allowing both static (compiled without -fPIC) and
+      shared object files (compiled with -fPIC) to exist side-by-side.
+      If you want to preserve the old behavior of using .o files for
+      shared objects, you must now explicitly reset the SHOBJSUFFIX
+      value in your construction environment as follows:
 
         env = Environment(SHOBJSUFFIX = '.o')
 
+  - The default behavior when no targets are specified has been changed
+    to be like Make: everything in the current directory and below will
+    be built.  This can be disabled by specifying "Default(None)" in an
+    SConscript, in which case there will be no default targets and
+    SCons will print an appropriate error message.
+
   - Setting the BUILDERS construction variable now properly clears
     the previous Builder attributes from the construction Environment.
     Before, you could initialize BUILDERS like so:
     If you have defined a strfunction() for a Python function Action,
     you will need to add a third "env" argument to your function call.
 
-  - The default behavior when no targets are specified has been changed
-    to be like Make: everything in the current directory and below will
-    be built.  This can be disabled by specifying "Default(None)" in an
-    SConscript, in which case there will be no default targets and
-    SCons will print an appropriate error message.
-
   Please note the following important changes since release 0.09:
 
     - The Scanner interface has been changed to make it easier to
     - Executing the -u or -U option from a source directory that has an
       associated BuildDir() does not build the targets in the BuildDir().
 
+    - Modifying a construction environment in a subsidiary SConscript
+      file modifies the global environment.
+
+    - PDB files on Win32 in a build that uses BuildDir() are built in
+      the source directory, not the build directory.
+
+    - MSVC .res files are not rebuilt when icons change.
+
+    - The -c option does not clean up .sconsign files or directories
+      created as part of the build.
+
     - No support yet for the following planned command-line options:
 
          -d -e -l --list-actions --list-derived --list-where