Hi Jack,
On 21/10/16 02:46, Jack Perdue wrote:
Howdy EB gods (Ken and crew),
So EB, puts some useful environment settings in
<app>/<version>/easybuild/<app>*-devel
Is there a way to utilize those variables when not
using EB?
For example, I assume that if a user loads icc that they
more than likely would like CC=icc (CFLAGS is a different
matter).
But EB doesn't do that now (probably for good reason).
It doesn't right now, no, but would it be interesting to add an option
to include statements to define the build environment as used by
EasyBuild in the toolchain module?
You can argue for it both ways, it's just a matter of what EasyBuild
should do by default (and we currently have a window of opportunity to
change the default behavior with EasyBuild 3.0 being the next release).
But it WOULD be nice if I could somehow use the variables in
the -devel file (in bash) without all the extraneous stuff.
Well, the devel modules were originally supposed to cover this need, but
they got broken a long time ago an nobody has cared enough to fix it
(even though, yes Markus, I'm going to say it, it shouldn't be hard to
fix those problems).
EB has a rich collection of useful environment variables
(especially when using Intel toolchains ala FFTW/LAPACK/BLAS)....
how can we make them available to the user (who just wants to
compile against EB modules without using EB).
As already mentioned by Miguel and Alan: --dump-env-script and the
BuildEnv generic easyblock could fulfill your need.
regards,
Kenneth
