You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Out of laziness, the waf tool boost was used copied into waf-tools/ in order to build against Boost. It is full featured but works differently from the rest. In particular, if one has a prefix with all dependencies one can not do:
$ ./wcb configure --prefix=$PREFIX
But, instead one must specifically notify the boost tool with:
When boost is not correctly directed will pick up the system install and the only indication is if the user notices a version match. Eg on Debian 12 we see
Checking boost includes : 1.74.0
instead of the desired Spack version:
Checking boost includes : 1.85.0
Probably the best solution it to hack boost.py tool to:
use "standard" --with-* type flags
make --boost-mt set by default
honor --prefix value as a potential location
The text was updated successfully, but these errors were encountered:
Out of laziness, the
waf
toolboost
was used copied intowaf-tools/
in order to build against Boost. It is full featured but works differently from the rest. In particular, if one has a prefix with all dependencies one can not do:But, instead one must specifically notify the
boost
tool with:When
boost
is not correctly directed will pick up the system install and the only indication is if the user notices a version match. Eg on Debian 12 we seeinstead of the desired Spack version:
Probably the best solution it to hack
boost.py
tool to:--with-*
type flags--boost-mt
set by default--prefix
value as a potential locationThe text was updated successfully, but these errors were encountered: