<html>#1775: Add Boost to ET
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Erik Schnetter</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>development version</td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>
<p>Comment (by tootle):</p>
<p>For my 2cents, I think it is an excellent idea to add a thorn that can detect boost libraries, but I think having to include the ability to build the whole library is too much bloat not to mention compile time. The number of dependencies that boost has in order to build the full suite is incredibly large - run spack concretize for a full boost spec and you’ll see what I mean. Even on our cluster, boost alone can take 30+ minutes to compile the full suite including dependencies. </p>
<p>I understand this goes against the ETK paradigm of everything that is needed is included, which should definitely be the case for fundamental components such as Carpet (glad to hear CarpetX will remove the boost dependency), but I think it would be more useful to fail gracefully and list the Thorns that depend on boost rather than defaulting to building the entire suite. Also, for modern clusters boost is usually available by default, but the environments may not be updated correctly making automated searches like those in Radice’s boost not robust. Cmake has incredibly good features for finding boost as well as individual components, but this still depends on the environment correctly setting `BOOST_ROOT`.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/1775/add-boost-to-et'>https://bitbucket.org/einsteintoolkit/tickets/issues/1775/add-boost-to-et</a></p>
</html>