diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-21 11:54:28 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-21 11:54:28 +0000 |
commit | e6918187568dbd01842d8d1d2c808ce16a894239 (patch) | |
tree | 64f88b554b444a49f656b6c656111a145cbbaa28 /src/boost/tools/build/test/duplicate.py | |
parent | Initial commit. (diff) | |
download | ceph-upstream/18.2.2.tar.xz ceph-upstream/18.2.2.zip |
Adding upstream version 18.2.2.upstream/18.2.2
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'src/boost/tools/build/test/duplicate.py')
-rw-r--r-- | src/boost/tools/build/test/duplicate.py | 38 |
1 files changed, 38 insertions, 0 deletions
diff --git a/src/boost/tools/build/test/duplicate.py b/src/boost/tools/build/test/duplicate.py new file mode 100644 index 000000000..6e65f9117 --- /dev/null +++ b/src/boost/tools/build/test/duplicate.py @@ -0,0 +1,38 @@ +#!/usr/bin/python + +# Copyright 2004 Vladimir Prus +# Distributed under the Boost Software License, Version 1.0. +# (See accompanying file LICENSE.txt or https://www.bfgroup.xyz/b2/LICENSE.txt) + +# This test tries to stage the same file to the same location by *two* different +# stage rules, in two different projects. This is not exactly good thing to do, +# but still, V2 should handle this. We had two bugs: +# - since the file is referred from two projects, we created to different +# virtual targets +# - we also failed to figure out that the two target corresponding to the copied +# files (created in two projects) are actually equivalent. + +import BoostBuild + +t = BoostBuild.Tester() + +t.write("a.cpp", """ +""") + +t.write("jamroot.jam", """ +build-project a ; +build-project b ; +""") + +t.write("a/jamfile.jam", """ +stage bin : ../a.cpp : <location>../dist ; +""") + +t.write("b/jamfile.jam", """ +stage bin : ../a.cpp : <location>../dist ; +""") + +t.run_build_system() +t.expect_addition("dist/a.cpp") + +t.cleanup() |