Databases
StackOverflow2013
Postsdbo
POIs there any way to prevent Boost.Build from recursively scanning header files for #include directives?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs there any way to prevent Boost.Build from recursively scanning header files for #include directives?
    primarykey
    data
    text
    <p>Is there a way to limit the header files that Boost.Build recursively scans for #include directives to a particular directory or set of directories? I.e. I'd like it to recursively scan the header files within my project only. I know that they external dependencies are not going to change (and being Boost and Qt they're pretty big). I end up with around 50,000 targets in the dependency tree which takes a while to process (resulting in a 1-2 minute build time even if no files have actually changed).</p> <p>The only solution I've found so far is to take advantage of the INCLUDE environment variable (I'm using MSVC) - this means Boost.Build need not be informed of the include paths (I'm using the feature) and hence will not scan them. This seems a bit of a hack.</p> <p>I feel like I must be missing something obvious because I haven't been able to find other people experiencing similar problems, even though I ran into this almost immediately. The closest I've come is <a href="http://www.nabble.com/BBv2-Slow-Startup-td20317427.html" rel="nofollow noreferrer">here</a>.</p> <p>Judging from the debug output (bjam -d 3) it also scans most of the header files more than once... I don't know if this means that they are added as dependencies more than once, but certainly the cost of loading a file and scanning the entire contents must add up?</p> <p>If I could tell it not to bother scanning a particular directory or set of directories in which I can guarantee the header files are not going to change, that would be perfect.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USWill Baker
    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.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIs there any way to prevent Boost.Build from recursively scanning header files for #include directives?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIs there any way to prevent Boost.Build from recursively scanning header files for #include directives?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POIs there any way to prevent Boost.Build from recursively scanning header files for #include directives?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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