Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to create simple Boost.Build make file containing links to libs I use on Windows and Linux?
    primarykey
    data
    text
    <p><code>main.cpp</code> which should be executable C++ app. It shall depend on</p> <ul> <li>Lib1 be a required to be compiled first (before main.cpp) project-lib (with lib1.h and lib1.cpp inside some separate folders)</li> <li>'Lib2.lib' with its dependency given precompiled libs (like cross-platform OpenCV for example)</li> </ul> <p>I need it to work for Windows and Linux and if possible Mac OS</p> <p>found for windows: look <a href="http://www.boost.org/doc/tools/build/doc/userman.pdf" rel="nofollow">here - "Common tasks"</a> page 26</p> <pre><code>exe hello : hello.cpp some_library.lib /some_project//library : &lt;threading&gt;multi ; </code></pre> <p>I hoped for better - more readable syntax form Boost creators... And BTW</p> <p>What the hell on earth does </p> <blockquote> <p>On Windows, if an application uses shared libraries, and both the application and the libraries are built using Boost.Build, it is not possible to immediately run the application, because the PATH environment variable should include the path to the libraries. It means you have to either add the paths manually, or have the build place the application and the libraries into the same directory.</p> </blockquote> <p>mean? I can not have a project with 2 nested project - one for .lib and one for app using that .lib? </p> <p>With this I see how to connect 1 .lib but how to connect a folder with them? And how to connect includes? And when I'll go to Linux what shall be changed? </p> <p>How should my bjam make/config file look like?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload