#!/usr/bin/python # Copyright 2003 Dave Abrahams # Copyright 2002, 2003, 2004 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) from BoostBuild import Tester t = Tester() t.write("project-root.jam", "import gcc ;") t.write("Jamfile", "lib a : a.cpp : . ;") t.write("a.cpp", """ #include void # ifdef _WIN32 __declspec(dllexport) # endif foo() {} """) t.write("a.h", "//empty file\n") t.write("d/Jamfile", "exe b : b.cpp ..//a ; ") t.write("d/b.cpp", """ void foo(); int main() { foo(); } """) t.run_build_system(subdir="d") # Now test the path features with condition work as well t.write("Jamfile", "lib a : a.cpp : debug:. ;") t.rm("bin") t.run_build_system(subdir="d") # Test path features with condtion in usage requirements t.write("Jamfile", "lib a : a.cpp : . : : debug:. ;") t.write("d/b.cpp", """ #include void foo(); int main() { foo(); } """) t.rm("d/bin") t.run_build_system(subdir="d") # Test that absolute paths inside requirements are ok. The problem # appear only when building targets in subprojects. t.write("project-root.jam", "") t.write("Jamfile", "build-project x ; ") t.write("x/Jamfile", """ local pwd = [ PWD ] ; project : requirements $(pwd)/x/include ; exe m : m.cpp : $(pwd)/x/include2 ; """) t.write("x/m.cpp", """ #include #include int main() {} """) t.write("x/include/h1.hpp", "\n") t.write("x/include2/h2.hpp", "\n") t.run_build_system() t.expect_addition("x/bin/$toolset/debug/m.exe") # Test that "&&" in path features is handled correctly. t.rm("bin") t.write("Jamfile", "build-project sub ;") t.write("sub/Jamfile", """ exe a : a.cpp : ../h1&&../h2 ; """) t.write("sub/a.cpp", """ #include int main() { return OK; } """) t.write("h2/header.h", """ const int OK = 0; """) t.run_build_system() t.expect_addition("sub/bin/$toolset/debug/a.exe") t.cleanup()