Lines Matching full:libraries

115 example, to control the location of external libraries. In many cases it
116 is better to declare those external libraries in the site-config.jam
173 On Unix-like operating systems, the order in which static libraries are
175 linker uses one pass though the libraries list. Passing the libraries in
194 The same approach works for searched libraries as well:
263 libraries. Shared libraries can be used by several applications, or
264 other libraries, without physically including the library in the
269 However, in order for application depending on shared libraries to be
274 `LD_LIBRARY_PATH` environment variable, or install the libraries to a
276 libraries are not yet ready to be installed, and cluttering system paths
281 because the build system knows the paths to all libraries and can
297 will allow the application to find libraries placed in the
300 If you install libraries to a nonstandard location and add an explicit
301 path, you get more control over libraries which will be used. A library
303 you install libraries to a system location and do not add any paths, the
307 Which approach is best depends on your situation. If the libraries are
310 libraries which can be used only by your application, it makes sense to
320 It is desirable to declare standard libraries available on a given
322 not really good, since locations of the libraries can vary between
344 [[bbv2.faq.header-only-libraries]]
345 == Header-only libraries
347 In modern {CPP}, libraries often consist of just header files, without any
348 source files to compile. To use such libraries, you need to add proper
350 of external libraries it becomes problematic to remember which libraries
356 Header-only libraries may be declared using the `alias` rule, specifying