[ptp-dev] Modules support for synchronized projects

[Jeffrey Overbey <jeffreyoverbey@xxxxxxx>]

I'm beginning to work on support for Environment Modules <http://modules.sf.net>.  We've discussed this a bit at NCSA, but I'd like to get feedback from others as well.

The plan is to target synchronized projects only, at least for now.  Remote and/or local projects could come later if there's demand and the relevant RDT/CDT developers are interested.

The set of modules that should be active during the build would be configured within the project properties and associated with the build configuration.  A UI prototype is below.  The initial selections would be based on the user's defaults (i.e., whatever "module list" returns).

At build time, we would start a non-interactive login shell (bash), and execute a sequence of module unloads, followed by a sequence of module loads, and finally make (and exit).  ("module purge" is supposed to unload all modules, but it segfaults on at least one test machine...)

After this works for build, we'll want to make modules available during launch, and we'd like to be able to use them to set remote include paths... but that's coming much later.

If anyone has comments/suggestions, I'd be interested to hear it.  I suspect many people on this list have spent more time with Modules than I have...