Vollstrecker

Seen that already while running the tests. Just skipped over to make the tests more robust as we have a race-condition in there before continuing with this one.

And maybe adding the lint to normal commits would also be a good idea to avoid the need of editing afterwards just because of a dot at the end.

And I guess the vars in the workflows could be revisited, as some (like build-type) are not needed or used anymore.

> Check this: https://github.com/abdes/cryptopp-cmake/blob/master/CONTRIBUTING.md#conventional-commits I know about this, but as I never came in touch with npm or all that stuff this would be just another packagemanager which throws stuff...

I guess this happens because we only handle Debug and Release, so the message saying this configuration is unknown, ist right. I know there is a way to tell cmake...

What do you mean with modifying the build env of parent? If you're talking about the property, this only sets the choices for the dropdown in cmake-gui but nonetheless it's...

Could you provide also the lines from the beginning of the config process and a config log of the working run so we can possible spot the differences? From what...

Just stumbled across this also. I've choosen 3.20.1 t avoid multiple match with the rc's of 3.20.0, but it still complains. Is there any way of getting rid f this?...

Not that I know anything about the internals of this topic, but does qbittorrent also print informations what it's doing? Maybe a comparision helps.

Unfortunately there is no easier way as libtool calculates the so-version in some "interessting" way. But from a quick look (with my mobile), the overall version should be matched correct...