Gcc and vcpkg have a concept of triplets. Leverage this practice or something similar to it so that the c++ build rules can find the right compiler and add the correct flags for the compilation. These should be installable on the same machine. Vcpkg already handles that by prefixing path with triplet, so there's likely nothing to do. It seems reasonable to require installer to specify independent install root for GULPACHEK_INSTALL_ROOT
gcc and msvc support have been added. testing with different architectures can be added when there's a use case to test against. closing for now and can be reopened when needed
Gcc and vcpkg have a concept of triplets. Leverage this practice or something similar to it so that the c++ build rules can find the right compiler and add the correct flags for the compilation. These should be installable on the same machine. Vcpkg already handles that by prefixing path with triplet, so there's likely nothing to do. It seems reasonable to require installer to specify independent install root for GULPACHEK_INSTALL_ROOT