enable_all_plugins="no"

option, parallelism,...

Moderators: fgoudreault, mcote

Forum rules
Please have a look at ~abinit/doc/config/build-config.ac in the source package for detailed and up-to-date information about the configuration of Abinit 8 builds.
For a video explanation on how to build Abinit 7.x for Linux, please go to: http://www.youtube.com/watch?v=DppLQ-KQA68.
IMPORTANT: when an answer solves your problem, please check the little green V-like button on its upper-right corner to accept it.
Locked
mverstra
Posts: 655
Joined: Wed Aug 19, 2009 12:01 pm

enable_all_plugins="no"

Post by mverstra » Mon Jun 14, 2010 9:14 am

I have found that the .ac file uses the enable_all_plugins="no" option to remove plugins. The command line still accepts --disable-all-plugins, but the .ac file ignores disable_all_plugins="yes"

1) the enable_all_plugins=no is ambiguous, as this could mean enable some plugins. I presume this is kind of true in that you can turn a few on by hand, but still...

2) why does the disable_all not work in the .ac file? This is the wierd.

Ciao

Matthieu
Matthieu Verstraete
University of Liege, Belgium

User avatar
pouillon
Posts: 651
Joined: Wed Aug 19, 2009 10:08 am
Location: Spain
Contact:

Re: enable_all_plugins="no"

Post by pouillon » Mon Jun 14, 2010 1:43 pm

There is nothing weird here in, as long as you know what is actually happening. ;)

The --disable-all-plugins option is a command-line alias. All --enable/--disable options are however translated by configure into enable_* environment variables. There cannot be disable_* variables, because it would open the way to inconsistencies and confusion. Indeed, when both exist, which one should you take?

I agree that the variable name is a little bit ambiguous. But in ~abinit/doc/config/build-config.ac, this ambiguity is doubly removed: it appears in "Maintainer options" and there is a warning.
Yann Pouillon
Simune Atomistics
Donostia-San Sebastián, Spain

Locked