In current git master (Audacity 3.0.4-alpha-20210816) as well as Audacity 3.0.3, Nyquist plugin support appears to be broken when compiled from source on Linux. When started with a fresh profile, no Nyquist plugins appear in the “Manage Plugins” window. If Nyquist plugins do appear on the list due to an existing profile, then they cannot be enabled. A git bisect reveals the following commit to have introduced this issue:
commit 6f58cb8294b1f52f960e0d7bde3d71a163193da4 Author: Paul Licameli <firstname.lastname@example.org> Date: Fri Feb 12 14:42:37 2021 -0500 Hoist the generation of the config header into top CMakeLists... ... Because it depends on having visited various lib-src directories, which I want to delay until visiting various of the modules, and I also want to visit src before the modules, because that's bottom-up dependency ordering. So the step should not be done in src. CMakeLists.txt | 11 +++++++++++ src/CMakeLists.txt | 11 ----------- 2 files changed, 11 insertions(+), 11 deletions(-)
Here is how I reproduce the bug:
- I am running KDE neon 5.22 User Edition, which is based on Ubuntu 20.04.
- I compile and install the software as follows, from within the “audacity” folder pulled down by github:
export DOCBOOK_TO_MAN="/usr/bin/docbook2x-man" mkdir build cd build cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Release -Daudacity_use_wxwidgets=local -Daudacity_use_ffmpeg=loaded .. make -j12 sudo make install
This installs everything with the default “/usr/local” prefix, including all the Nyquist plugins into “/usr/local/share/audacity/plug-ins/”
3. Delete “~/.audacity-data” to start with a clean profile.
4. Start Audacity.
5. Go to “Effect” → “Add / Remove Plug-ins…”
Result: None of the Nyquist plugins installed to “/usr/local/share/audacity/plug-ins” appear in the list. If the plugins do appear due to being referenced in an existing “~/.audacity-data” profile, they will all be disabled, and cannot be enabled.
Expected result: Nyquist plugins from “/usr/local/share/audacity/plug-ins” and “~/.audacity-data/Plug-Ins” should appear and be able to be enabled.