I’m trying to compile Audacity, and, can’t get past the following step:
“Build the “help” project by enabling it in the MS Visual Studio
Configuration Manager (Build menu). This will download a copy of the
Manual wiki onto your machine and copy it to the correct place for
your build. If the local copy needs to be updated, run
and re-build the “help” project.”
Is this really required for a full build of Audacity? Can I just skip and still build this? Not that I don’t want the help one, but, I need to build fast.
Compile.txt assumes some foreknowledge or at least willingness to search and navigate other web pages. Otherwise it would slow down users who already have some experience in compiling programs and then they would be complaining.
You can never build in 10 minutes from scratch. It takes at least 40 minutes to install the correct SDK, Visual Studio, and then build both Widgets and Audacity - if you have done it before and know what you are doing.
If you have specifics about “carelessness”, please collect the specifics together and post them in a new topic in this board.
I’ll volunteer to test your instructions.
I rarely use Windows at all these days and gave up trying to build on Windows when I kept running into bugs in the free version of VS, but I’d be delighted to follow detailed step-by-step instructions.
That was my first attempt.
I then tried it on a real, (but old) hardware with little more success. At that time I didn’t really have the will or inclination to persevere with something that appeared so convoluted and long winded on Windows, that could be done so easily on my preferred OS.
Let’s try step 1:
Get Microsoft VC++ 2008 (this is the compiler you will need—it is free from Microsoft). You may get the 32-bit version (which will work on 64-bit) here: Microsoft VC++ 2008
Where exactly on that page do I click to download Microsoft VC++ 2008 ?
The later “Windows SDK for Windows 8” doesn’t target Windows XP so it would not be any use to Audacity Team, and there are questions on the web (but no answers) as to whether “Windows SDK for Windows 8” supports VS2008.
AFAICT from the end of that topic, the latest problem was that the update was choking trying to check legacy security updates for Internet Explorer which were irrelevant because the past updates were already cumulated into current updates.
So with the legacy updates deprecated, that problem should be fixed, and all should be OK assuming the user also has in place all other current IE fixes for issues that were causing their own hang.
I remember another gotcha now. Even if you download the VS2008 installer without SP1 which is itself only a few kb, the drive being downloaded to must have enough space to install VS even if you are not installing VS there. Otherwise, the installer hangs when you run it.
It also affects automatic update. Fixing the problem when it breaks is a pain, especially on single processor machines, because the computer just grinds to a halt as soon as the update service starts (which by default is automatic on start up). There are conspiracy theories about Microsoft doing it deliberately to drive users off XP, which don’t sound at all far fetched if you experience the problem first hand