Installing software in your home directory: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Marked this version for translation)
No edit summary
Line 44: Line 44:


<!--T:21-->
<!--T:21-->
In some cases, however, particularly with <tt>cmake</tt>, it may be necessary to specify explicitly the location of the library provided by the modulefile. The preferred and the most robust way to do so is to use an EasyBuild environment variable, <tt>EBROOT...</tt>, instead of manually typing a path. This will allow you to switch easily between toolchains without modifying the compilation instructions, and will also reduce the risk of linking a mismatched library. For example, if you need to specify the location of the GSL library, the option you provide to <tt>cmake</tt> might look like <tt>-DGSL_DIR=$EBROOTGSL</tt>. The <tt>EBROOT...</tt> environment variables adhere to the same construction pattern: <tt>EBROOT</tt> followed by the name of the package, for example <tt>EBROOTGCC</tt>.
In some cases, however, particularly with <tt>cmake</tt>, it may be necessary to specify explicitly the location of the library provided by the module. The preferred and the most robust way to do so is to use an EasyBuild environment variable, <tt>EBROOT...</tt>, instead of manually typing a path. This will allow you to switch easily between toolchains without modifying the compilation instructions, and will also reduce the risk of linking a mismatched library. For example, if you need to specify the location of the GSL library, the option you provide to <tt>cmake</tt> might look like <tt>-DGSL_DIR=$EBROOTGSL</tt>. The <tt>EBROOT...</tt> environment variables adhere to the same construction pattern: <tt>EBROOT</tt> followed by the name of the package, for example <tt>EBROOTGCC</tt>.


== BLAS/LAPACK and MKL == <!--T:10-->
== BLAS/LAPACK and MKL == <!--T:10-->
rsnt_translations
53,464

edits

Navigation menu