Since the juce repo contains all versions of juce, why aren’t you just checking out an older version when you need it? Are you modifying the source, maintaining your own fork or something?
I don’t understand this step. There are already VisualStudio2015, VisualStudio2017, and VisualStudio2019 folders under extras/Projucer/Build. You don’t need the old Projucer to generate the build system files to build the new one.
I had the same thing happen after accepting an upgrade to 5.4.5. Yesterday, i also accepted an updated to Visual Studio, so maybe that’s related. Here is how I resolved it: Somehow the VS project file had its default build target set back to VS 2017, which I have never used or had on the system:
VS2019: Project/Properties: Set platform toolset to 2019 v142.
I have no idea why this happened, but I’m also quite new to Juce, so with that: switching back to 5.4.4 and setting the VS tools as above, the project compiled. Switching to 5.4.5, the toolchain got reset to v141, so I think projucer does this.
I am a solo programmer, I simply use a good depth of backups, which allows me to roll back, if necessary. This has always been sufficient for my needs.
How do you develop across multiple machines, like a laptop and desktop, or a machine running Windows and another running OS X? Please don’t say “I keep my source code in DropBox”.
This does not address the issue, however. When downloaded, the JUCE Zip file does not contain a compiled “ProJucer.exe”, so it is necessary to compile one for yourself. It is therefore necessary to use your existing version of ProJucer (in my case, Version 5.4.4) to compile the new version (5.4.5 in this instance). This has always worked in the past, no problem. But with the 5.4.5 release, it is not working for VS 2017, as I reported in my initial post. And, see above, I am not the only one.
So, something is different with the 5.4.5 version, at least as far as VS 2017 is concerned.
I can continue to work using the 5.4.4 version of JUCE. But I like to be on the latest version, so I am hoping someone can offer a solution, as I have not found one.
This is what everyone does. The repo includes Xcode project files, and Visual Studio project files. You don’t need a previous version of ProJucer to build Projucer. See here:
Thank you. Compiling directly from the VS solution file worked, of course.
I do all my work within VS 2017. And, in my three years experience with JUCE, I have always passed any code related to JUCE through Projucer, including Projucer itself, on its way to VS… And this was never a problem until now.
I suspect the JUCE guys have tired of people having issues caused by compiling with older mismatched versions of JUCE and Projucer, so they have now made that an error.
Going forward I know to use the VS solution file directly.
You should learn to use Git so you can pull the develop branch from the official repo into your local copy so you stay up to date with all the bug fixes they push out every few days:
The situation was resolved by simply using the Visual Studio solution file directly. And the situation arose from my habit of always passing anything JUCE related through the Projucer. So, it had been my habit to build the new Projucer by using the previous version Projucer. But now that produces an error and will not compile. So, going forward, I will always compile the new Projucer directly from the Visual Studio solution file.
I suspect the JUCE team got tired of people having issues due to mismatched versions of JUCE and Projucer, and so made that an error?
