From 0d6f835ffb582296d24a8d1dd479e2703e075ee3 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Fri, 18 Oct 2019 14:05:03 +0200 Subject: Add ability to specify "compiler mode" options as part of config.{c,cxx} Such options are (normally) not overridden by buildfiles and are passed last (after cc.coptions and {c,cxx}.coptions) in the resulting command lines. They are also cross-hinted between config.c and config.cxx. For example: $ b config.cxx="g++ -m64" --- libbuild2/cc/msvc.cxx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'libbuild2/cc/msvc.cxx') diff --git a/libbuild2/cc/msvc.cxx b/libbuild2/cc/msvc.cxx index e7251ac..a85e7a0 100644 --- a/libbuild2/cc/msvc.cxx +++ b/libbuild2/cc/msvc.cxx @@ -220,7 +220,8 @@ namespace build2 msvc_header_search_paths (const process_path&, scope&) const { // The compiler doesn't seem to have any built-in paths and all of them - // come from the INCLUDE environment variable. + // either come from the INCLUDE environment variable or are specified + // explicitly on the command line. // @@ VC: how are we going to do this? E.g., cl-14 does this internally. // cl.exe /Be prints INCLUDE. @@ -239,7 +240,8 @@ namespace build2 msvc_library_search_paths (const process_path&, scope&) const { // The linker doesn't seem to have any built-in paths and all of them - // come from the LIB environment variable. + // either come from the LIB environment variable or are specified + // explicitly on the command line. // @@ VC: how are we going to do this? E.g., cl-14 does this internally. // cl.exe /Be prints LIB. -- cgit v1.1