No subject

but not a shell script (which seems to be the machinery behind the
'module' command).

What you can do however is to identify which environment change did the
module unload do and then do the same with cmake.

You may be able to monitor the change from cmake using a shell script
which does:

env > file1
module unload
env > file2
diff file1 file2

--> then process the diff ouput with some cmake script
en reproduce the environnement change using
set(ENV{EnvVarName} "newValue")
--=20
Erk
Membre de l'April - =AB promouvoir et d=E9fendre le logiciel libre =BB -
http://www.april.org