ceph/src/boost/tools/build/test/searched_lib.py

   1 #!/usr/bin/python
   2
   3 # Copyright 2003 Dave Abrahams
   4 # Copyright 2003, 2004, 2005, 2006 Vladimir Prus
   5 # Distributed under the Boost Software License, Version 1.0.
   6 # (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt)
   7
   8 # Test usage of searched-libs: one which are found via -l
   9 # switch to the linker/compiler.
  10
  11 import BoostBuild
  12 import os
  13 import string
  14
  15 t = BoostBuild.Tester(use_test_config=False)
  16
  17
  18 # To start with, we have to prepare a library to link with.
  19 t.write("lib/jamroot.jam", "")
  20 t.write("lib/jamfile.jam", "lib test_lib : test_lib.cpp ;")
  21 t.write("lib/test_lib.cpp", """\
  22 #ifdef _WIN32
  23 __declspec(dllexport)
  24 #endif
  25 void foo() {}
  26 """);
  27
  28 t.run_build_system(subdir="lib")
  29 t.expect_addition("lib/bin/$toolset/debug/test_lib.dll")
  30
  31
  32 # Auto adjusting of suffixes does not work, since we need to
  33 # change dll to lib.
  34 if ( ( os.name == "nt" ) or os.uname()[0].lower().startswith("cygwin") ) and \
  35     ( BoostBuild.get_toolset() != "gcc" ):
  36     t.copy("lib/bin/$toolset/debug/test_lib.implib", "lib/test_lib.implib")
  37     t.copy("lib/bin/$toolset/debug/test_lib.dll", "lib/test_lib.dll")
  38 else:
  39     t.copy("lib/bin/$toolset/debug/test_lib.dll", "lib/test_lib.dll")
  40
  41
  42 # Test that the simplest usage of searched library works.
  43 t.write("jamroot.jam", "")
  44
  45 t.write("jamfile.jam", """\
  46 import path ;
  47 import project ;
  48 exe main : main.cpp helper ;
  49 lib helper : helper.cpp test_lib ;
  50 lib test_lib : : <name>test_lib <search>lib ;
  51 """)
  52
  53 t.write("main.cpp", """\
  54 void helper();
  55 int main() { helper(); }
  56 """)
  57
  58 t.write("helper.cpp", """\
  59 void foo();
  60 void
  61 #if defined(_WIN32)
  62 __declspec(dllexport)
  63 #endif
  64 helper() { foo(); }
  65 """)
  66
  67 t.run_build_system(["-d2"])
  68 t.expect_addition("bin/$toolset/debug/main.exe")
  69 t.rm("bin/$toolset/debug/main.exe")
  70
  71
  72 # Test that 'unit-test' will correctly add runtime paths to searched libraries.
  73 t.write("jamfile.jam", """\
  74 import path ;
  75 import project ;
  76 import testing ;
  77
  78 project : requirements <hardcode-dll-paths>false ;
  79
  80 unit-test main : main.cpp helper ;
  81 lib helper : helper.cpp test_lib ;
  82 lib test_lib : : <name>test_lib <search>lib ;
  83 """)
  84
  85 t.run_build_system()
  86 t.expect_addition("bin/$toolset/debug/main.passed")
  87 t.rm("bin/$toolset/debug/main.exe")
  88
  89
  90 # Now try using searched lib from static lib. Request shared version of searched
  91 # lib, since we do not have a static one handy.
  92 t.write("jamfile.jam", """\
  93 exe main : main.cpp helper ;
  94 lib helper : helper.cpp test_lib/<link>shared : <link>static ;
  95 lib test_lib : : <name>test_lib <search>lib ;
  96 """)
  97
  98 t.run_build_system(stderr=None)
  99 t.expect_addition("bin/$toolset/debug/main.exe")
 100 t.expect_addition("bin/$toolset/debug/link-static/helper.lib")
 101 t.rm("bin/$toolset/debug/main.exe")
 102
 103 # A regression test: <library>property referring to searched-lib was being
 104 # mishandled. As the result, we were putting target name to the command line!
 105 # Note that
 106 #    g++ ...... <.>z
 107 # works nicely in some cases, sending output from compiler to file 'z'. This
 108 # problem shows up when searched libs are in usage requirements.
 109 t.write("jamfile.jam", "exe main : main.cpp d/d2//a ;")
 110 t.write("main.cpp", """\
 111 void foo();
 112 int main() { foo(); }
 113 """)
 114
 115 t.write("d/d2/jamfile.jam", """\
 116 lib test_lib : : <name>test_lib <search>../../lib ;
 117 lib a : a.cpp : : : <library>test_lib ;
 118 """)
 119
 120 t.write("d/d2/a.cpp", """\
 121 #ifdef _WIN32
 122 __declspec(dllexport) int force_library_creation_for_a;
 123 #endif
 124 """)
 125
 126 t.run_build_system()
 127
 128
 129 # A regression test. Searched targets were not associated with any properties.
 130 # For that reason, if the same searched lib is generated with two different
 131 # properties, we had an error saying they are actualized to the same Jam target
 132 # name.
 133 t.write("jamroot.jam", "")
 134
 135 t.write("a.cpp", "")
 136
 137 # The 'l' library will be built in two variants: 'debug' (directly requested)
 138 # and 'release' (requested from 'a').
 139 t.write("jamfile.jam", """\
 140 exe a : a.cpp l/<variant>release ;
 141 lib l : : <name>l_d <variant>debug ;
 142 lib l : : <name>l_r <variant>release ;
 143 """)
 144
 145 t.run_build_system(["-n"])
 146
 147
 148 # A regression test. Two virtual target with the same properties were created
 149 # for 'l' target, which caused and error to be reported when actualizing
 150 # targets. The final error is correct, but we should not create two duplicated
 151 # targets. Thanks to Andre Hentz for finding this bug.
 152 t.write("jamroot.jam", "")
 153 t.write("a.cpp", "")
 154 t.write("jamfile.jam", """\
 155 project a : requirements <runtime-link>static ;
 156 static-lib a : a.cpp l ;
 157 lib l : : <name>l_f ;
 158 """)
 159
 160 t.run_build_system(["-n"])
 161
 162
 163 # Make sure plain "lib foobar ; " works.
 164 t.write("jamfile.jam", """\
 165 exe a : a.cpp foobar ;
 166 lib foobar ;
 167 """)
 168
 169 t.run_build_system(["-n", "-d2"])
 170 t.fail_test(string.find(t.stdout(), "foobar") == -1)
 171
 172
 173 # Make sure plain "lib foo bar ; " works.
 174 t.write("jamfile.jam", """\
 175 exe a : a.cpp foo bar ;
 176 lib foo bar ;
 177 """)
 178
 179 t.run_build_system(["-n", "-d2"])
 180 t.fail_test(string.find(t.stdout(), "foo") == -1)
 181 t.fail_test(string.find(t.stdout(), "bar") == -1)
 182
 183 t.cleanup()