How do I make an installer after a successfull compiling


I need some advise as to how to make an installer for audacity after I successfully compiled the source code. I recompiled Audacity because I wanted to incorporate ASIO with 2.0.1 version. First of all I need to tell you that I do not have experience in this type of programming. So please do not just give me a very simple descriptopm with a lot of the technical stuff that a competent programmer should have known already. I compiled 2.0.1 according to the instructions by Edgar who has a posting in this forum. The link is in the compiling error for libsndfile. I got 25 successes, 0 errors, 0 skips and 0 up to date. However, I had a lot of warnings, like type mismatch, integer/float/bolean, etc. I have a Windows 7, ultimate, 32 bit box. Now, I need to install this re-compiled version to my computer. How do I do it? Please specify any further software, download links, etc.

Thank you.

P.S. I found this link,, but it is not very helpful because I do not have experience in this type of programming. I’ve never created any installer before.

I’ve not compiled in Windows, but I don’t think that you need to make an installer just to run Audacity. As far as I’m aware you should be able to run Audacity from the build directory. Have you tried running your fresh build of Audacity?


I have not because I do not know that. There are many files in the Build directory and which one should I click to run. In addtion, I would like to transfer the new compilation to my second computer to record music. In this case, do I need to build the installer?


If Audacity has built correctly there will be a file called “audacity.exe”. That is the “executable” file and you should be able to run it by double clicking on it.

Building an installer is fairly straight-forward. No programming is necessary, the developers have already taken care of that.
Download and install the latest Unicode Inno Setup QuickStart Pack self-installing package. (
During the installation of Inno Setup, answer yes to any extras the installation suggests to download.

In the “win” directory of the source tree, you’ll find the file audacity.iss:
Double-click on it and the Inno Setup installer creator will start up:
Click on the compile button (the button the mouse pointer is resting on in the picture above) or press Ctrl+F9.

Inno Setup builds the Audacity installer and places the result in the winOutput directory:
That’s all there’s to it.



There is no Build directory in the source code file after compiling and I could not find any audacity.exe anywhere. I will try to make an executable for audacity using the recommendation from another viewer.


Excellent! That means that the build has succeeded.
You should find the Audacity executable audacity.exe in the winUnicode Release directory.

This is normal.


Hello Ragnar:

I found the .exe file and it worked. Thank you. I have another question. What is the difference between opening Audacity by using .exe and install Audacity first by using an installer? As a matter of fact, I want to install Audacity to another computer to record music. In this case, is an installable version a better choice to move Audacity to another computer? Or I can just copy the compiled source code and paste it to another computer.

At this time, the choice I have for the drivers are MME and Windows directive sound driver. But I did not see ASIO. Do I need to download this driver first? I know I do not have this driver installed right now. Before the compilation, I did download all the “Steinberg Stuff” from their site, so the capability using ASIO should be with this new compiled version. Is my assumption correct"


If you are not replacing an existing installation of Audacity there is little benefit from installing. The installation creates a file association for .aup Audacity project files. If you do not install Audacity then on first run you will be asked if you want to associate .aup files with Audacity. Either way you can move the .exe installer or a folder containing all the following to the new computer


This assumes you built Unicode Release. If you built Unicode Debug, the widgets dll’s will have “28ud” in their name, not “28u”.

To be precise you have to install the ASIO SDK from Steinberg ( Select Company, then Developer.

If you defined an environment variable called ASIOSDK_DIR pointing to the base directory of the ASIO SDK and received no related errors then you will see the ASIO host when you have connected an ASIO enabled sound device, or are using third-party ASIO drivers like ASIO4ALL.

Please note that if you built Audacity with ASIO support you must not distribute it (or the installer) to anyone else.


Thank you guys for all the information. That is all the questions I have for now. I will play around with it for a few days and I might have more questions later on. When I do, I will come back.