<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 Roland Haas):</p>
<p>If and when we include Boost in the ET I would strongly advertise to include the whole <a data-is-external-link="true" href="http://thing.Ie" rel="nofollow">thing.Ie</a> there is one “Boost” thorn that provides everything. Splitting up Boost into <code>Boost_FileSyste</code> and <code>Boost_SpecialFunctions</code> etc similar to what eg Debian’s package manger does, just buys into lots of dependency issues. </p>
<p>To me the goal of ExternalLibraries is to provide a simple, working fallback and way to for Cactus thorns to interface with the 3rd party libs. It should not become a full featured package management system since we lack resources to maintain that. If this means it is slow the relying on fallback compilation, then so be it. If it is slow all the time even when mostly not used (OpenSSL is in that category if it compiles) then this may be an issue. </p>
<p>Generally I feel that expecting a 5minute compile time, without any prior experience and expecting a fully optimized build that way is not realistic for a scientific code. I certain level of experience of the user is expected, at least if they desire an “optimized” build.</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>