From: Valentin Samko (boost.build_at_[hidden])
Date: 2005-06-12 15:09:53
I just experienced the same problem using bbv2 on a computer where
vc7.1 was installed in c:\bin\msvc.2003, and not in "....NET 2003".
VP> The issue is that V2 takes a conservative approach. Unless we're sure that
VP> compiler is 7.0+, we don't pass the option, since earlier compilers did not
VP> have it.
Wouldn't it make sense to call cl.exe from msvc.jam, and get the
version number from its output?
VP> Does using explicit
VP> using msvc : 7.1 ;
VP> helps? What is your installation path?
Yes, that helped, thanks. Still, why rely on the path, when we can use
the output of cl.exe ?
Also, with bbv1 I could specify the version of vc++ in the command
line (by specifying a different msvc toolset). Is this possible with
bbv2?
-- Valentin Samko http://val.samko.info