Commits

Anonymous committed 873596e

Prepare the release.

  • Participants
  • Parent commits 0fe3d9c

Comments (0)

Files changed (4)

 BUILDING 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:
+We 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
 

File debian/changelog

 
   * Eighth post-official-Debian build cycle
 
- -- Steven Knight <knight@baldmt.com>  Mon, 31 Mar 2003 20:22:00 -0600
+ -- Steven Knight <knight@baldmt.com>  Wed, 21 May 2003 05:16:32 -0500
 
 
 scons (0.13-1) unstable; urgency=low

File src/CHANGES.txt

 
 
 
-RELEASE 0.14 - XXX
+RELEASE 0.14 - Wed, 21 May 2003 05:16:32 -0500
 
   From Chad Austin:
 

File src/RELEASE.txt

 
 
 
-RELEASE 0.14 - XXX
+RELEASE 0.14 - Wed, 21 May 2003 05:16:32 -0500
 
   This is the fourteenth 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.13:
 
-  - Tool specifications no longer take a "platform" argument.
-    XXX
+  - Tool specifications no longer take a "platform" argument.  You
+    will need to remove this argument if you define any local Tool
+    specifications.  The new env['PLATFORM'] construction variable can
+    now be used to find the string that used to be passed in as the
+    "platform" argument.
 
   - Emitter functions in Builders are now passed Node objects, not
     strings, for all targets and sources.  Your emitter may need to
     now take a fourth "for_signature" argument that is set when the
     expansion is being called to generate a build signature.
 
+  - Construction variables for building a target are now frozen when the
+    Builder is called; later changes to the Environment do not
+    necessarily affect how the target is build.  You may need to
+    re-order statements in your SConscript files to make sure
+    construction variables are set before calling the Builders that will
+    use them.
+
   Please note the following important changes since release 0.11:
 
   - The default behavior of SCons is now to change to the directory in
     - 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
       (for example) \some\target is the same as X:\some\target (for your
       current volume X:).
 
+    - .sconsign files can be written even when the -n option is used,
+      possibly causing incorrect "up to date" builds the next time around.
+
+    - An explicit target beginning with "../" (i.e. above the current
+      directory) is ignored when using the -u, -U or -D options.
+
     - No support yet for the following planned command-line options:
 
          -d -e -l --list-actions --list-derived --list-where
         Charles Crain
         Steve Leblanc
         Anthony Roach
-        Terrel Shumway
+        Greg Spencer
+        Christoph Widemann