No installation is necessary. The unzipped archive provides the command line tools ready to use. I strongly advise against making system-wide changes to the PATH environment variable. Instead point your IDE to the full paths of the tools you want to use. An example on how to do this for Code::Blocks is explained here: https://winlibs.com/#usage-codeblocks For Visual Studio Code it should be pretty much the same. I do you hope you mean Visual Studio Code (the IDE) and not the full Visual Studio programming...
Thanks. Do you normally consider master to be stable enough for production?
Release version / release schedule
undefined reference to `xb::operator<<(std::ostream&, xb::xbString const&)
Use -static-libstdc++ / -static-libstdc++ in combination with -static so not only standard libraries are statically linked, but also any others (like -lwinpthread).
Sure, my build script is published here: https://github.com/brechtsanders/winlibs_recipes/blob/main/recipes/xbase64.winlib
I figured out how to build 4.1.0 with MinGW-w64. I just used the build/debian/CMakeLists.txt after applying the following changes: patch -ulbf build/debian/CMakeLists.txt << EOF @@ -370,6 +370,6 @@ # Microsoft Windows settings -IF( WIN32 ) +IF( MSVC ) # add_definitions( /D_CRT_SECURE_NO_WARNINGS) add_definitions( /EHsc ) -ENDIF( WIN32 ) +ENDIF( MSVC ) @@ -707,3 +707,3 @@ -install (FILES include/xbconfig.h +install (FILES \${PROJECT_BINARY_DIR}/include/xbconfig.h \${PROJECT_SOURCE_DIR}/include/xbase.h...
Correction, I see some CMakeLists.txt files under build/* but which one is for MinGW-w64?