From 58efd51dc4f71b9fd25ecc9ee3198e9949a2a8dc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jurko=20Gospodneti=C4=87?= Date: Sun, 22 Feb 2009 17:34:25 +0000 Subject: [PATCH] Added a comment specifying several alternative implementations for the common.file-creation-command rule on Windows. [SVN r51395] --- src/tools/common.jam | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/src/tools/common.jam b/src/tools/common.jam index d37c14d7a..20f52d52e 100644 --- a/src/tools/common.jam +++ b/src/tools/common.jam @@ -559,6 +559,23 @@ rule file-creation-command ( ) { 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