GNOME Bugzilla – Bug 570990
No way for the user to disable building a specific plugin
Last modified: 2020-04-24 15:16:14 UTC
Right now there is no way for the user to disable building of specific plugins. We should add an option to disable building of specific plugins, i.e. --disable-plugin=[plugin name here]
I agree, that we need some way to disable specific plugins. Unfortunately the --disable, but also --without don't work like that. They throw errors if you add an argument. But --enable-plugins=.... works, but is not intentional. Something I could imagine too is to use AC_ARG_VAR to define a variable DISABLED_PLUGINS. The variable then needs to be given to configure ./configure DISABLE_PLUGINS=foo,bar PS: I think of defining this in a macro, which takes a list of possible optional plugins (not all plugins should be optional, correct?). The given list of diabled plugins then should be compared to the list of plugins defined to be optional. Depending on the result, some variable should be defined. It will need some time to write this down and test it, because I'm currently pretty busy. But now you know the plan :)
*** Bug 601811 has been marked as a duplicate of this bug. ***
Hi, if this ticket is still valid in a recent version of Bluefish, then please report this under https://sourceforge.net/p/bluefish/tickets/ as GNOME Bugzilla is not used anymore by the Bluefish developers - thanks a lot!