While CMake is full of crap and it is entirely a nessissary evil, but a porject on none MSVC generates *.lib, *.a or *.dll with th prefix "lib" while a CMAKE_STATIC_LIBRARY_PREFIX and CMAKE_SHARED_LIBRARY_PREFIX were forced to an empty string is a whole new level of crapeness!
My LinkedIn been inactive for quite sometime, recetly i opened the account again & that was thier greetings message!
Every service doing that forcing AI to be ON by default (yes, you hear me @github.com) is NASTY!
let's make Visual Studio great again!!😄
"VS Pets" is super cute & funny weird extension (VS22, VS26, VSCode) that gives some life to VS! Didn't expect to see such a thing (MP3 Dancer & Winamp days) and didn't expect to install it!
marketplace.visualstudio.com/items?itemNa...
if you maybe wondering why would i waste part of the project's time in keeping it compatible ancient C++ on Windows and outside the limited scope of MSVC+VS, it is simply because my engine supporting many old platforms natively, and i always want to keep that while moving fwd.
U may find some attempts for Ninja on Win, but i cancelled them early, as it didn't seem to integrate well on VSCode.
I wanted to be able to generate project for any platform/console for any C++ver(98->23), & ninja wasn't helping in getting a ready project in the IDE of choice.
how would you expect humans to unify, where we not yet unified on \ and / in paths between Windows, Linux, MSVC and MinGW 😄
funny how much comments ending in a cmake file vs the actual cmake logic!😄
(green lines for pure comments and blue lines for URL comments)
After many attemps (see my recycle bin deletion count) and fighting w CMake, the engine now can compile MinGW/G++ on Windows (along side MSVC or Ninja/G++ Linux)
This was a very important step, as unfortunatly moving to latest versions of VS took away old C++11/03/98 from me!
