Age | Commit message (Collapse) | Author | Files | Lines |
|
configuration variables are specified for dependent
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
constraint
|
|
|
|
|
|
|
|
different configuration clusters
|
|
|
|
|
|
|
|
|
|
|
|
|
|
explicitly specified
Now, if configuration is not specified for a system dependency package, then
it is assumed to be specified for all current configurations and their
explicitly linked configurations, recursively, including private
configurations that can potentially be created during this run.
|
|
|
|
|
|
For projects with a large number of dependencies (e.g., Boost) these can take
a while.
|
|
then from just main database
|
|
|
|
|
|
|
|
|
|
|
|
|
|
options for cfg-create
|
|
Now that a package name can include a configuration, using just spaces is
insufficient.
|
|
|
|
Wrong selection was causing redundant prerequisites recollection.
|
|
|
|
|
|
|
|
case-insensitively on Windows
|
|
|
|
|
|
|
|
|
|
!config.dist.bootstrap=true'
|