Please excuse the rewarming of this topic…
I’d like to make a case for keeping the static library projects for Windows, and for reviving them for MacOS.
We use the buildbot method in our development to create binaries for other developers and testers. For a number of reasons the servers always build from fresh checkouts - but using prebuilt Juce libraries. There may be others out there who do the same, and are fervidly hoping for this as well??
** We have a regular plethora of Juce apps in our source trees. Building the Juce sources for each app and variant on each commit will make the build times close to unworkable for us, even though our build machines are mighty beasties.
We fully understand that it isn’t possible to provide a static library project (especially for XCode) that has the proper defaults for everyone’s purposes, but they’ve always been an extremely useful starting point. Perhaps you could include an #error directive in a project header file, with a caveat saying that “A library project can’t anticipate all appropriate build settings. Not intended to be turn-key, so no nastygrams on the forums please.” ??
If the static library projects disappear, we would look into maintaining them separately of course.
I was glad to find a Juce 2.0-related project in git for MacOS (removed before the release), and used that as a starting point to get updated to Juce 2.0, and it saved a lot of development time.
** If there is a great deal of code reorganizing in the future we’d not have that advantage again.
There are a couple of other key reasons we like the static lib projects. If you’re open to the idea I can elaborate a bit more.