How to compile LSQuic on Windows?

[Guthib-of-Dan]

I am currently trying to refactor build.c (parallelised it and Linux build is several times faster + gonna PR soon, don't you mind?), however Windows doesn't want to build LSQuic.

This script fails

Error message:
( it was compiling well until lsquic_versions_to_string.c ls-sfparser.c showed up)

lsquic\src\liblsquic\lsquic_versions_to_string.c(26,18): error C2059:
syntax error: ')' [lsquic\src\liblsquic\lsquic.vcxproj]
lsquic\src\liblsquic\lsquic_versions_to_string.c(42,18): error C2059:
syntax error: ')' [lsquic\src\liblsquic\lsquic.vcxproj]
lsquic\src\liblsquic\lsquic_versions_to_string.c(64,35): warning C403
4: sizeof returns 0 [lsquic\src\liblsquic\lsquic.vcxproj]
Generating Code...
Done Building Project "lsquic\src\liblsquic\lsquic.vcxproj" (default
targets) -- FAILED.

Done Building Project "lsquic\ALL_BUILD.vcxproj" (default targets) --
FAILED.

Build FAILED.

"

"lsquic\ALL_BUILD.vcxproj" (default target) (1) ->
"lsquic\src\liblsquic\lsquic.vcxproj" (default target) (3) ->
(ClCompile target) ->
lsquic\src\liblsquic\lsquic_versions_to_string.c(26,18): error C205
9: syntax error: ')' [lsquic\src\liblsquic\lsquic.vcxproj]
lsquic\src\liblsquic\lsquic_versions_to_string.c(42,18): error C205
9: syntax error: ')' [lsquic\src\liblsquic\lsquic.vcxproj]

1 Warning(s)
2 Error(s)

[Guthib-of-Dan]

And also if uWebSockets.js repo doesn’t do any changes to its dependencies, maybe it would be better to use something like vcpkg and skip manual zlib, boringssl, lsquic compilation? Fetch them ready and have no troubles at all. I can do that in fork and PR.

If you have any reasons to avoid package managers, then how do I compile lsquic?

[uNetworkingAB]

Package managers are the most malware infested, resting supply chain attack pieces of shit ever invented by mankind. They are almost always controlled by non-authors and change "maintainers" in very promiscuous, glaringly insecure ways. Building all deps from a fix git submodule is a trillion galaxies better in every measurable way. In fact, Git as software deployment overall is a trillion times more secure than package managers.

[uNetworkingAB]

I did an audit on NPM and found that, if I remember correctly, the top 50 modules all had their overwhelming majority of deps non-determined. That's frankly put, extremely retarded and fully insane. It's literally an open flesh wound. You have a moving target and you argue that this is "immutability". The entire NPM piece of shit is built on fundamental deep rooted retardation and achieves nothing of use more than encouraging promiscuous use of deps, supply chain attacks and fanatical following "because everyone is". Retardation is what it is.

[Guthib-of-Dan]

Understandable. Then maybe make some commits that push those prebuilt dependencies for all platforms to another branch like “binaries”? Make GitHub Action that compiles them all and displays as artifacts, then we manully populate branch like “binaries” and create another script that just fetches them each time we clone repository (like postinstall). It can be even some script that we har in package.json a. In the same way we can resolve “installation size problem” - create “postinstall” script on package.json that fetches needed binary “.node” as soon as someone installs uWebSockets.js

But all that is a dream while I still can’t compile lsquic

[Guthib-of-Dan]

Maybe not even push them to a branch, but to a release, not as one .tar.gz, but each binary separately. If they are snapshotted then we literally create a stable archive and can fetch them when needed. Result: git submodules as a fallback, specialised installation, 2 types of releases (1 - uWS binaries, 2 - rarely changing dependencies), faster builds, preserved stability

[Guthib-of-Dan]

Emm, compilation is still not working. I looked through almost everything and current script differs a lot from what works for me. And not just works, but “lets Perl start”. That Perl script inside lsquic seems broken, because it doesn’t generate normal versions_c… file. Official docs in lsquic are outdated and they use vcpkg. I will try to compile that with vcpkg on windows, because I can’t PR those Linux build scripts alone.

[Guthib-of-Dan]

Fighting with manifest mode of vcpkg is even worse, bad idea. So:

How to compile LSQuic on Windows?

[uNetworkingAB]

The world does not owe you an explanation,

That said, I don't even know what you are trying to do. We already have CI jobs that compile all deps on all platforms and they work beautifully, the recipe for doing so already is stated in the GitHub Actions workflow file. I'm not going to read it for you, and I have no interest in modifying any of that stuff.

[uNetworkingAB]

It's literally here under build_lsquic

uWebSockets.js/build.c

Line 103 in baef293

run("cd uWebSockets/uSockets/lsquic && cmake -DCMAKE_C_FLAGS=\"/Wv:18 /DWIN32 /wd4201 /I..\\..\\..\\zlib-1.3.1\" -DZLIB_INCLUDE_DIR=..\\..\\..\\zlib-1.3.1 -DCMAKE_POSITION_INDEPENDENT_CODE=ON -DCMAKE_MSVC_RUNTIME_LIBRARY=MultiThreaded -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DBORINGSSL_DIR=../boringssl -DCMAKE_BUILD_TYPE=Release -DLSQUIC_BIN=Off . && msbuild ALL_BUILD.vcxproj");

[Guthib-of-Dan]

And I literally can’t run it, as stated above. Then I’ll just leave it as is.