To bring this a little more up to date here are the command line methods that worked successfully for me to include ASIO support. I use an admin terminal.
Download the current release source:-
git clone -b release-3.7.4 --depth 1 https://github.com/audacity/audacity/ audacity3_7_4
Use build.md to make sure all the pre-requisites are installed. Then run cmake as follows:-
cmake -G "Visual Studio 17 2022" -DCMAKE_CONFIGURATION_TYPES=Release -Daudacity_has_asio_support=On -DAUDACITY_BUILD_LEVEL=2 -S D:\audacity3_7_4 -B d:\audacity3-7-4
Provided cmake completes correctly you should find the file ALL_BUILD.vcxproj in the top level of your target folder. Open this in Visual Studio 2022 and build the project. Once built the local windows debug option should confirm all OK.
Personally I am not an experienced Audacity user I just use it to produce very high quality analogue to digital recordings so I can’t help with much else.
I used the approach that was documented, but have encountered the following error:
-- Configuring incomplete, errors occurred!
libpng/1.6.39@audacity/stable: ERROR:
Package '20dedd443066e18460760f9b45470113ab48de0a' build failed
libpng/1.6.39@audacity/stable: WARN: Build folder C:\Users\User\.conan2\p\b\libpndb89a4f2e6762\b\build
ERROR: libpng/1.6.39@audacity/stable: Error in build() method, line 136
cmake.configure()
ConanException: Error 1 while executing
Generating options profile...
Traceback (most recent call last):
File "D:\audacity3_7_4\conan\conan_runner.py", line 109, in <module>
subprocess.check_call(conan_options, stdin=subprocess.DEVNULL)
~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Apps\Python\Python313\Lib\subprocess.py", line 419, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['conan.exe', 'install', 'D:\\audacity3_7_4\\conan', '--build=missing', '--output-folder', 'D:/audacity3-7-4', '--remote', 'audacity-binaries-conan2', '--profile:build', 'D:\\audacity3-7-4\\conan\\profiles\\build.profile', '--profile:host', 'D:\\audacity3-7-4\\conan\\profiles\\host-debug.profile']' returned non-zero exit status 1.
CMake Error at cmake-proxies/cmake-modules/AudacityDependencies.cmake:209 (message):
Conan failed to install dependencies (1)
C:/Apps/Python/Python313/python.exe
Call Stack (most recent call first):
CMakeLists.txt:592 (include)
If anyone can help solve my installation problem, I’d be very grateful. I had a working Audacity 3.7.4 build system under Windows 10 Pro x64, but can’t seem to get it working under Windows 11 Pro x64.
When you upgraded to Windows 11, was it on the same computer, or a new one?
It sure looks like Python isn’t installed, or Visual Studio can’t find it.
It was the same computer, but I did a completely fresh install of Windows 11. When I open up a PowerShell console, I have Python installed:
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows
PS C:\Users\User> python
Python 3.13.5 (tags/v3.13.5:6cb20a2, Jun 11 2025, 16:15:46) [MSC v.1943 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>>
And cmake, conan, and pip are found.
PS C:\Users\User> conan --version
Conan version 2.18.1
PS C:\Users\User> cmake --version
cmake version 4.1.0-rc2
CMake suite maintained and supported by Kitware (kitware.com/cmake).
PS C:\Users\User> pip --version
pip 25.1.1 from C:\Apps\Python\Python313\Lib\site-packages\pip (python 3.13)
Are you using power shell or command prompt for the cmake command? I’m not sure if PS works and also administrator mode is required. D drive output directory may exist but must be empty. Delete any temporary files from previous attempts.
It turns out that the culprit preventing me from building Audacity 3.7.4 under Windows 11 was none other than CMake Release Candidate 4.1.0-rc2. When I removed 4.1.0-rc2 from my system and replaced it with CMake 3.31.8, I was able to get CMake to produce the requisite Visual Studio solution files. Using those I was able to successfully build Audacity 3.7.4.
Being curious, I have also tried using CMake 4.1.0-rc3. The Audacity 3.7.4 build process was able to be completed successfully, which is comforting:
Build started at 11:44 AM...
1>------ Build started: Project: ZERO_CHECK, Configuration: Release x64 ------
1>1>Checking Build System
2>------ Build started: Project: version, Configuration: Release x64 ------
3>------ Build started: Project: twolame, Configuration: Release x64 ------
4>------ Build started: Project: sqlite, Configuration: Release x64 ------
5>------ Build started: Project: soundtouch, Configuration: Release x64 ------
3>Building Custom Rule D:/audacity3_7_4/cmake-proxies/twolame/CMakeLists.txt
2>Building Custom Rule D:/audacity3_7_4/src/CMakeLists.txt
6>------ Build started: Project: portsmf, Configuration: Release x64 ------
4>Building Custom Rule D:/audacity3_7_4/cmake-proxies/sqlite/CMakeLists.txt
6>Building Custom Rule D:/audacity3_7_4/cmake-proxies/portsmf/CMakeLists.txt
3>ath.c
3>availbits.c
3>bitbuffer.c
3>crc.c
3>dab.c
:
125>------ Build started: Project: ALL_BUILD, Configuration: Release x64 ------
125>Building Custom Rule D:/audacity3_7_4/CMakeLists.txt
126>------ Skipped Build: Project: PACKAGE, Configuration: Release x64 ------
126>Project not selected to build for this solution configuration
127>------ Skipped Build: Project: INSTALL, Configuration: Release x64 ------
127>Project not selected to build for this solution configuration
========== Build: 119 succeeded, 0 failed, 0 up-to-date, 8 skipped ==========
========== Build completed at 11:52 AM and took 08:37.397 minutes ==========
1 Like
Thanks. I’ve taken the liberty of marking your post as a solution.
1 Like