Package Details: audacity-git 3.6.3.r257.g652bfea82-1

Git Clone URL: https://aur.archlinux.org/audacity-git.git (read-only, click to copy)
Package Base: audacity-git
Description: A program that lets you manipulate digital audio waveforms
Upstream URL: https://www.audacityteam.org/
Keywords: audio editor
Licenses: GPL2, CCPL
Groups: pro-audio
Conflicts: audacity
Provides: audacity, ladspa-host, lv2-host, vamp-host, vst-host, vst3-host
Submitter: proudzhu
Maintainer: None
Last Packager: ongyx
Votes: 16
Popularity: 0.37
First Submitted: 2015-11-02 16:13 (UTC)
Last Updated: 2024-09-10 16:47 (UTC)

Dependencies (48)

Required by (143)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 9 Next › Last »

FabioLolix commented on 2023-08-29 17:30 (UTC)

Also need rapidjson at least as makedepends

    PortAudio_LIBRARIES: /usr/lib/libportaudio.so
CMake Error at /build/audacity-git/src/build/find_package_include.cmake:17 (find_package):
  By not providing "FindRapidJSON.cmake" in CMAKE_MODULE_PATH this project
  has asked CMake to find a package configuration file provided by
  "RapidJSON", but CMake did not find one.

  Could not find a package configuration file provided by "RapidJSON" with
  any of the following names:

    RapidJSONConfig.cmake
    rapidjson-config.cmake

Dylan14 commented on 2023-08-29 16:59 (UTC)

VST3_SDK_DIR needs to be changed to /usr/src/vst3sdk.

NotReallyEight commented on 2023-05-04 11:53 (UTC)

Hello, I was trying to install this, but I get the following error when compiling: CMake Error at cmake-proxies/cmake-modules/Findvst3sdk.cmake:56 (message): Failed to build VST3SDK Call Stack (most recent call first): /home/notreallyeight/.cache/yay/audacity-git/src/build/find_package_include.cmake:18 (find_package) cmake-proxies/cmake-modules/AudacityDependencies.cmake:217 (include) CMakeLists.txt:572 (include)

What could be the cause? All the needed dependencies are installed at least from what I can see from the required dependencies.

ongyx commented on 2022-10-30 16:25 (UTC)

@evorster Thanks for the suggestions, I've modified the PKGBUILD accordingly to build Audacity entirely against system libs. Turns out there was a audacity_conan_enabled CMake flag, so I set it to off and added the necessary dependencies.

evorster commented on 2022-08-27 04:12 (UTC) (edited on 2022-08-27 04:12 (UTC) by evorster)

Hi there! After some poking around, here are working build instructions:


prepare() {
mkdir -p build
}

build() {
 cd build
 cmake -G "Unix Makefiles" ../audacity \
    -DCMAKE_BUILD_TYPE=Release \
    -DCMAKE_INSTALL_PREFIX=/usr \
    -Daudacity_use_ffmpeg=loaded \
    -Daudacity_lib_preference=system \
    -Daudacity_has_vst3=Off \
    -Daudacity_use_wxwidgets=local \
    -Daudacity_obey_system_dependencies=On
  make
}
package() {
make -C build DESTDIR="${pkgdir}" install
}


Warning

There are serious issues with the way that this builds, though. Firstly, it creates a .conan directory in your home directory where it builds wxWidgets 3.1.3

Then, it links against wxWidgets against gtk2, which needs to be installed in your system. At least there are GUI on the plugins. :)

Also, vst3sdk does not build with conan, and it does not detect system vst3sdk if installed, so vst3 plugins are disabled with this build.

If anyone knows how to build tell build scripts to build against wxWidgets installed in a custom location, then we can build against wxgtk3-dev-314-opt from AUR. (please post a comment here)

Long term I am chatting to the fine folk at Audacity to see if we can make the latest version of wxWidgets work properly in Audacity, and to detect system vst3sdk.

jlocash commented on 2022-07-24 19:46 (UTC)

To disable conan and force the build to use system libraries use -Daudacity_conan_enabled=Off -Daudacity_obey_system_dependencies=On when running cmake. You can then build against the wxWidgets you have installed (built for GTK2 or 3).

Note: if building with gcc-11, the build will fail to build against wxWidgets > 3.1.4 because of a change in wxEvtHandler that was introduced in wxWidgets-3.1.5.

ongyx commented on 2022-01-14 15:32 (UTC) (edited on 2022-01-14 16:23 (UTC) by ongyx)

To build Audacity against GTK3, it seems the solution is to ditch conan totally and force it to build only against system libraries.

EDIT: Apparently it's not possible to patch in wxgt3 so Audacity can link against it. Short of patching the special wxwidgets/3.1.3.2-audacity conan package ourselves, I don't see any other way.

magnus-tesshu commented on 2022-01-14 07:29 (UTC) (edited on 2022-01-14 11:31 (UTC) by magnus-tesshu)

As far as I can tell, building wxwidgets with conan doesn't honor wxBUILD_TOOLKIT=gtk3 any longer, and it now generates a gtk2 wxwidgets. I haven't found a way to fix this yet.

This is very annoying. I'm trying to install this, but I don't have gtk2 installed anymore. It fails to build. Any idea why that might be happening?

EDIT: looking into it, a configure script from conan is the problem. I'm presently setting random environment variables to see if one of them gets it to ignore its default and use GTK3.

EDIT2: Doesn't appear like any environment variables will do the trick. wxBUILD_TOOLKIT is not found by grep anywhere in audacity anymore, I'm going to look at when it was removed to see if anything else is also missing

This is commit 70bbfb69d5006950ef3e6a21078ece0771beacfe. At that time, they didn't use conan to install wxWidgets-audacity and so it is unlikely that a simple solution exists.

If you go to the directory that conan downloads wxWidgets to you can run cmake -DwxBUILD_TOOLKIT=gtk3 and it will work, but audacity doesn't pass the arguments over to it in its build process. I have no idea how conan or the Cmake language works so I don't know if it is possible to get conan to do this on its own.

Refutationalist commented on 2021-11-04 05:42 (UTC)

As far as I can tell, building wxwidgets with conan doesn't honor wxBUILD_TOOLKIT=gtk3 any longer, and it now generates a gtk2 wxwidgets. I haven't found a way to fix this yet.

fab4fab commented on 2021-10-27 10:52 (UTC)

@ongyx thank you for your reply, now working perfectly.