gtafan wrote: ↑Thu Jul 23, 2020 1:23 pm
That comandline is a bit longer, at least if you want to have it build the way you want.
What are you missing in the command line compared to the official build (static vs shared aside)? That is how I build wxWidgets for myself with MSVC (the only difference there is using nmake instead of mingw32-make). If you want another options, you cannot use prebuilt wxWidgets binaries anyway? Even if you wanted to use more options, you just copy and paste the options once, save the command as a batch and you are done for ever.
gtafan wrote: ↑Thu Jul 23, 2020 1:23 pm
Static libraries have 1 huge advantage, you have just 1 single executable files, which you can use on as much PCs with the coresponding OS as you want, and no need to provide all that crapy dlls.
Distributing DLLs in 21st century is no big deal, pretty much every popular programs does that, even in the portable version. Static linking, in particular the CRT, has also many disadvantages and is generally not recommended, feasible, or even with some libraries possible.
Just out of curiousity, which other C++ compiled libraries are you familiar with, providing prebuilt static binaries for a large range of compilers? To me it seems you are not very experienced in C++: compared to other large libraries, wxWidgets build extremely easily, painlessly (as they have no external dependencies, at least on MSW), and quick.
gtafan wrote: ↑Thu Jul 23, 2020 1:23 pm
So even if it´s just 10 minutes, let say just 1000 people use the API, makes 10000 minutes wasted.
Not sure what API are you talking about. You also seem to confuse CPU time with human time. You can let the build go in the background, you do not need to fearfully stare at the scary command line window all the time the build is going on. Additionally, compared to resources wasted in other ways, building wxWidgets
gtafan wrote: ↑Thu Jul 23, 2020 1:23 pm
Also system environment variable has nothing to do with C++, at least as long you are using no external APIs, so you could said wxWidgets is not for me.
Even a power user knows how to use system environment variables, it is a must for a real programmer. When building wxWidgets, one commonly uses at least PATH and WXWIN (strongly recommended by the wxWidgets Team). But hey, finally something we can agree on: wxWidgets and C++ seems to be not the best fit for you. ;)