From a user perspective it would be more interesting to have this option under Lmod than EB. The end user is most likely to interact only with the environment modules manager than EB directly. The idea would be that the user loads all the modules he/she needs according to a specific toolchain and can get all the linking flags by calling something like:
$module -L In this way the user can use command substitution directly into Makefiles. More importantly, this should also take into account ordering the lib flags accordingly since sometimes order is essential for successful linking. That is something that we discussed internally since this functionality is provided by our current modules manager (although in a very primitive way) and would be lost when transitioning to Lmod. -- Davide Vanzo, PhD Application Developer Adjunct Assistant Professor of Chemical and Biomolecular Engineering Advanced Computing Center for Research and Education (ACCRE) Vanderbilt University - Hill Center 201 (615)-875-9137 www.accre.vanderbilt.edu On Oct 22 2016, at 8:12 am, Jack Perdue <[email protected]> wrote: On 10/22/2016 02:47 AM, Kenneth Hoste wrote: > 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). I'd definitely like to see it as an option. For testing, --dump-env-script on ImageMagick-7.0.3-2-intel-2016b.eb would be a good start. I'd like to see _everything_ set in that .env instead set in the modules first... as just a start. Beyond that, I'd also like to see a line with -lX11 -lXabc -lX123 so I don't need to remember the name of all the X11 libs. But it should be a site (or user) selectable option (I could see some people not wanting such things). jack (who won't be making it to Utah but does have new cluster coming online and has the ability to provide beer through his agents)
