Torrust-Tracker won't compile on Windows

[Power2All]

Just tried to compile this on Windows CLion with Rust.
These modules are not compatible with Windows:

• ring
• libz-sys
• libsqlite3-sys
• openssl-sys

You might want to look into replacing these, or looking to remove them.
Unless of course, you won't want to support multi-platforms.

[Power2All]

Found the problem why it won't compile on Windows.
You use OpenSSL, which breaks.
Would advice to switch to Rustls, which does compile correctly on all platforms.

[josecelano]

Found the problem why it won't compile on Windows. You use OpenSSL, which breaks. Would advice to switch to Rustls, which does compile correctly on all platforms.

Thank you @Power2All. I have to spend some time to understand the problem. Rigth now I only know:

• We changed here the openssl dependency to vendored.
• We have had some problems because of this because in fact, we need other system dependencies like make. See Compilation error: failed to run custom build command for openssl-sys v0.9.85 #319.

I think we should:

1. Decide which platforms we want to support.
2. Make sure the app compiles for all of them.
3. Add a workflow to check cross-compilation as I mentioned here.

I guess we want to support Windows unless there is a major performance issue or something like that. I think there is no active contributor using Windows for development right now.

cc @da2ce7 @WarmBeer

[Power2All]

We changed #68 the openssl dependency to vendored.

I tried this too, but didn't work out as expected, as it's force to use MSVC, which you definitely don't want to use for compiling.

I've fixed all the issues on my end by skipping most of these -sys libraries it tries to use.
OpenSSL seems to be the only issue, it does this in combination with ring library, hence the issue.

I think there is no active contributor using Windows for development right now.

Before most of the changes, I was the one using Windows, with CLion as IDE.
Since I've been too busy with other projects, I wasn't paying attention on the changes on Torrust-Tracker (I've noticed RwLock is a performance hit, like a lot, compared when using Crossbeam Channel for mutex read and write actions, which I will be trying to work out anyway).