summaryrefslogtreecommitdiff
path: root/tools/build/v2/test/double_loading.py
diff options
context:
space:
mode:
Diffstat (limited to 'tools/build/v2/test/double_loading.py')
-rw-r--r--tools/build/v2/test/double_loading.py30
1 files changed, 30 insertions, 0 deletions
diff --git a/tools/build/v2/test/double_loading.py b/tools/build/v2/test/double_loading.py
new file mode 100644
index 0000000000..27004a1767
--- /dev/null
+++ b/tools/build/v2/test/double_loading.py
@@ -0,0 +1,30 @@
+#!/usr/bin/python
+
+# Copyright 2003 Vladimir Prus
+# Distributed under the Boost Software License, Version 1.0.
+# (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt)
+
+import BoostBuild
+
+t = BoostBuild.Tester()
+
+# Regression test for double loading of the same Jamfile.
+t.write("jamroot.jam", "" )
+t.write("jamfile.jam", "build-project subdir ;")
+t.write("subdir/jamfile.jam", 'ECHO "Loaded subdir" ;')
+
+t.run_build_system(subdir="subdir")
+t.expect_output_line("Loaded subdir")
+
+
+# Regression test for a more contrived case. The top-level Jamfile refers to
+# subdir via use-project, while subdir's Jamfile is being loaded. The motivation
+# why use-project referring to subprojects is useful can be found at
+# http://article.gmane.org/gmane.comp.lib.boost.build/3906/
+t.write("jamroot.jam", "" )
+t.write("jamfile.jam", "use-project /subdir : subdir ;")
+t.write("subdir/jamfile.jam", "project subdir ;")
+
+t.run_build_system(subdir="subdir");
+
+t.cleanup()