Answers to these and all compiling related questions can be asked and answered on discord: https://discord.gg/kdrFa8vk
Checkout channel Windows (COMPILING AUDACITY)
I did get the latest audacity source to compile with ASIO support. The below instructions are for noobs like myself.
I started with a fresh Windows installation and installed the following software:
Visual Studio 19, version 16.11.15, Desktop development with C++ workload
CMake-gui 3.21.4
Python 3.10.0
conan 1.41.00
git 2.33.1
When installing the above , when there is choice to add the software to the Windows PATH variable then do so. After installing the software above, the steps to compile with ASIO support is as follows:
create a directory for the audacity source (i.e. c:\audacity)
create a directory for the build output (i.e. c:\audacity-build)
open a command shell in the audacity source directory
Following steps above, how do I resolve these errors in CMake “Configure”? Where do I find conan installer? This on Win 10 x64. Thanks.
EDIT: Sorry, found conan. Trying again…
EDIT2: Still got errors, but this process reminded me that I am not ready to upgrade to x64 Audacity as I have a few VST plugins that are x86. Sorry for the confusion.
Admin: Feel free to delete this post. I tried, but prohibited.
This is a great post!!
What surprises me is it doesn’t seem to need C:\asiosdk_2.3.3 to be created and set in the environment variables?
I also needed to move c:\audacity\audacity to c:\audacity before running CMake.
And by default Debug is selected in Visual Studio 19 you may want to change to the Release Version before compiling.
Aside from these this post is dead on an easy to follow!!! And no missing DLL’s either!
I was able to use this to compile Audacity! I can now use my old UA-101 and UA-1000 to record multiple microphones!
I have a question though. After compiling, I found the .exe in the C:\audacity-build\Debug folder. I was also able to copy the whole debug folder to another Windows 10 computer and open it there. Did I do that right? or is there a better way? Thanks for your help!
A couple of updates during the compiling process: I needed to use Visual Studio 2022 17 and I had to downgrade my conan to version 1.59. 0
It sounds like your build configuration may be set to “Debug” mode instead of “Release” mode. The .exe is normally posted to the ~\Release folder when the project is correctly set to “Release” mode in the build configuration.