[Boost-commit] svn:boost r51395 - trunk/tools/build/v2/tools

Subject: [Boost-commit] svn:boost r51395 - trunk/tools/build/v2/tools
From: jurko.gospodnetic_at_[hidden]
Date: 2009-02-22 12:34:25

Author: jurko
Date: 2009-02-22 12:34:25 EST (Sun, 22 Feb 2009)
New Revision: 51395
URL: http://svn.boost.org/trac/boost/changeset/51395

Log:
Added a comment specifying several alternative implementations for the common.file-creation-command rule on Windows.
Text files modified: 
   trunk/tools/build/v2/tools/common.jam |    17 +++++++++++++++++                       
   1 files changed, 17 insertions(+), 0 deletions(-)

Modified: trunk/tools/build/v2/tools/common.jam
==============================================================================
--- trunk/tools/build/v2/tools/common.jam	(original)
+++ trunk/tools/build/v2/tools/common.jam	2009-02-22 12:34:25 EST (Sun, 22 Feb 2009)
@@ -559,6 +559,23 @@
 {
     if [ os.name ] = NT
     {
+        # A few alternative implementations on Windows:
+        #
+        #   'type NUL >> '
+        #        That would construct an empty file instead of a file containing
+        #      a space and an end-of-line marker but it would also not change
+        #      the target's timestamp in case the file already exists.
+        #
+        #   'type NUL > '
+        #        That would construct an empty file instead of a file containing
+        #      a space and an end-of-line marker but it would also destroy an
+        #      already existing file by overwriting it with an empty one.
+        #
+        #   I guess the best solution would be to allow Boost Jam to define
+        # built-in functions such as 'create a file', 'touch a file' or 'copy a
+        # file' which could be used from inside action code. That would allow
+        # completely portable operations without this kind of kludge.
+        #                                            (22.02.2009.) (Jurko)
         return "echo. > " ;
     }
     else