$include_dir="/home/hyper-archives/boost-build/include";
include("$include_dir/msg-header.inc")
?>
- Next message: Chris Drexler: "Re: [jamboost] Re: BBv2: one library, two compilers (win: cl, icl)"
- Previous message: Vladimir Prus: "Re: [jamboost] BBv2: one library, two compilers (win: cl, icl)"
- In reply to: David Abrahams: "Re: BBv2: one library, two compilers (win: cl, icl)"
- Next in thread: Chris Drexler: "Re: [jamboost] Re: BBv2: one library, two compilers (win: cl, icl)"
- Reply: Chris Drexler: "Re: [jamboost] Re: BBv2: one library, two compilers (win: cl, icl)"
David Abrahams wrote:
> That's not the way I intended for intel support to work, though it
> seems to be a decent stopgap measure. intel is supposed to be a
> vendor variant, so that we can have an intel.jam toolset which
> inherits from msvc and sets the vendor.
I've actually tried
using msvc : : "P:/Program Files/Microsoft Visual Studio/vc98" : :
vcvars32-p.bat ;
using msvc : : "P:/Program Files/Something" : intel : vcvars32-p.bat icl ;
Together with
exe a : a.cpp b ;^M
obj b : b.cpp : <toolset-msvc:vendor>intel ;
But it causes all compiles to be done with intel: seems like
<toolset-msvc:vendor>intel is the default value.
- Volodya
- Next message: Chris Drexler: "Re: [jamboost] Re: BBv2: one library, two compilers (win: cl, icl)"
- Previous message: Vladimir Prus: "Re: [jamboost] BBv2: one library, two compilers (win: cl, icl)"
- In reply to: David Abrahams: "Re: BBv2: one library, two compilers (win: cl, icl)"
- Next in thread: Chris Drexler: "Re: [jamboost] Re: BBv2: one library, two compilers (win: cl, icl)"
- Reply: Chris Drexler: "Re: [jamboost] Re: BBv2: one library, two compilers (win: cl, icl)"
$include_dir="/home/hyper-archives/boost-build/include";
include("$include_dir/msg-footer.inc");
?>