Just prettify build.c + setbuf, added .gitignore.

[Guthib-of-Dan]

I literally did almost nothing extraordinary, just put newlines for compilation commands, log sections like lsquic/boringssl/linking, "setbuf" to see logs immediately in GitHub Actions.

Added "-DCMAKE_OSX_DEPLOYMENT_TARGET=12.0 " to MacOS builds because GitHub Actions used to flood with logs about version mismatch. These lines of code literally force MacOS-12, while GitHub Actions use MacOS-15:

    /* Apple special case */
    build("clang -target x86_64-apple-macos12",
          "clang++ -stdlib=libc++ -target x86_64-apple-macos12",
          "-undefined dynamic_lookup" MACOS_LINK_EXTRAS,
          OS,
          X64);

    /* Try and build for arm64 macOS 12 */
    build("clang -target arm64-apple-macos12",
          "clang++ -stdlib=libc++ -target arm64-apple-macos12",
          "-undefined dynamic_lookup" MACOS_LINK_EXTRAS,
          OS,
          ARM64);

As you can see here https://github.com/Guthib-of-Dan/uWebSockets.js/actions/runs/24628414774, everything compiles successfully. And PR is just about readability + pretty simple

[uNetworkingAB]

nmake is part of Visual C++, but this step is not nmake, it's nasm (Netwide Assembler). Is nasm really part of the default GitHub Action images?

[Guthib-of-Dan]

How interesting. It compiles... Alright. I'll uncomment that. We lose nothing in the end of the day
Just a minute

[Guthib-of-Dan]

Done

[Guthib-of-Dan]

if ( this PR is reviewed ) {
// Is it going to be merged?
// Or I can make next commits to it that will be reviewed one by one? Surely if I make one commit, I will wait until it is accepted before making next. I got such thought due to the whole idea of transforming build, which ... consists of a few steps
}
Actually if something goes wrong reverting commit makes one more commit, so it is better to make several pull requests.

Just thoughts aloud.