<html>#426: Fortran module files should not go into scratch directory
<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></td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Cactus</td></tr>
</table>
<p>Changes (by Roland Haas):</p>
<p><table>
<tr><td>assignee:</td><td>Roland Haas (was )</td></tr>
<tr><td>responsible:</td><td>[] (was )</td></tr>
</table></p>
<p>The Cactus build system currently cds into the configuration's scratch directory before compiling any file, and accumulates all Fortran module (.mod) files there. This results in a very large directory, and does not separate thorns from each other. This also makes it difficult to delete all built files from a single thorn, which is often convenient for debugging.</p>
<p>Instead, Fortran module files should be written into the thorn's object directory. Cactus should then set the Fortran include path correctly so that other thorns' module files are found, if this thorn declared the dependency onto the other thorns.</p>
<p><strong>Keyword:</strong></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/426/fortran-module-files-should-not-go-into'>https://bitbucket.org/einsteintoolkit/tickets/issues/426/fortran-module-files-should-not-go-into</a></p>
</html>