Steffen André Langnes

I would love to participate in a future discussion about the direction of the build system, CMake, etc. I think the only thing I would like to address in this...

As for breaking changes, one that is going to be immediately apparent (aside from files being moved/renamed) is that that the scripts do not by default do anything now except...

I would actually like to decouple the library's build scripts from consumers where possible. One question is who should bear the responsibility to make the WebView2 library available on Windows....

I came up with this snippet for easily fetching WebView2: ``` cmd /c (if not exist libs\webview2 mkdir libs\webview2) ^ && curl -sSL "https://www.nuget.org/api/v2/package/Microsoft.Web.WebView2" ^ | tar -xf - -C...

Now that I have confirmed that the library can be built and used in a pure C++ program on Windows entirely using MinGW-w64, it could make sense to be able...

Because the CI job for Windows takes longer now, I have attempted to split it up into x64 and x86. Linting takes a good chunk of time since it's done...

I think I'm happy with how the build has been split now. It will run lint checks while the main build is on-going to get feedback sooner. I also disabled...

With #773 being merged, the user-facing instructions for using the library ("getting started") have been decoupled from the build scripts. Does that in any way change the stance on whether...

I am not sure if it would be much different from running commands manually but I can imagine that Python has a lot of third party packages available through pypi...

One more thing is debugging the library. That's one thing I would like to address properly.