fwcd

Also note that `pull_request` builds run in the context of the targeted repo (i.e. PRs here will build in the context of this repo) whereas `push` builds will run in...

I'll close this since there doesn't seem to be that much interest in handling this edge case, given that most feature branches are in forks anyway. The only rather common...

Did you click "Yes" in the notification fhat prompted you to install the Kotlin language server?

The first time you open a Kotlin file you should get a prompt, similar to this:  If it isn't shown you might find it in the lower right corner...

You can also manually download the language server from [here](https://github.com/fwcd/kotlin-language-server/releases) and then point `kotlin.languageServer.path` to the binary, but I'd recommend the automatic installation if possible, since that will update the...

Yes, it's only useful if both release and debug builds are installed. The `vcpkg` environments (including those downloaded by the buildenv scripts) ship both versions for all dependencies, though. >...

Applying it to all libraries instead of just a few targets actually should be pretty easy to do, as outlined in [the stackoverflow post](https://stackoverflow.com/a/57223840), just add this before the first...

Though I could also see the use in allowing debug builds at least for some smaller libraries, even when just using release Qt + every else in debug mode, Mixxx...

In that case, simply defaulting `CMAKE_BUILD_TYPE` to `Release` or `RelWithDebInfo` should do the trick, I think? (IMO, the `QT_RELEASE` flag feels orthogonal to this, since it's intended as a small,...

Any updates on this? Being able to compile Mixxx with full debug symbols, assertions etc. while linking a release build of Qt would be pretty useful (I'm happy to resolve...