Note that there are some explanatory texts on larger screens.

plurals
  1. POhow to overcome building error when I'm using bcp to export boost thread?
    primarykey
    data
    text
    <p>I'm using boost <em>bcp</em> tool to export <em>thread</em> library from boost. The layout of exported library is</p> <pre><code>- Jamroot + libs |----- + thread |----- + build |----- - Jamfile.v2 + boost + doc </code></pre> <p>Now when I run <em>bjam</em> in build library is getting me :</p> <pre><code>boostcpp.jam: No such file or directory ../../../Jamroot:138: in modules.load rule boostcpp.set-version unknown in module Jamfile&lt;/Users/miladrezayee/Softwares/developer/boost_1_53_0/tmp1&gt; /Users/miladrezayee/Softwares/developer/boost_1_53_0/tools/build/v2/build/project.jam:317: in load-jamfile /Users/miladrezayee/Softwares/developer/boost_1_53_0/tools/build/v2/build/project.jam:62: in load /Users/miladrezayee/Softwares/developer/boost_1_53_0/tools/build/v2/build/project.jam:115: in load-parent /Users/miladrezayee/Softwares/developer/boost_1_53_0/tools/build/v2/build/project.jam:430: in initialize /Users/miladrezayee/Softwares/developer/boost_1_53_0/tools/build/v2/build/project.jam:308: in load-jamfile /Users/miladrezayee/Softwares/developer/boost_1_53_0/tools/build/v2/build/project.jam:62: in load /Users/miladrezayee/Softwares/developer/boost_1_53_0/tools/build/v2/build/project.jam:168: in project.find /Users/miladrezayee/Softwares/developer/boost_1_53_0/tools/build/v2/build-system.jam:570: in load </code></pre> <p>I exported <em>system</em> libray and when I run *bjam in build folder, it compiles successfully. I don't why <em>thread</em> library can't compile? Anybody have any idea what is going wrong with <em>thread</em> library?</p>
    singulars
    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