Re: [Boost-build] Patch to clear Intel /Op deprecated warning

Subject: Re: [Boost-build] Patch to clear Intel /Op deprecated warning
From: Beman Dawes (bdawes_at_[hidden])
Date: 2011-11-28 09:50:56

Vladimir Prus <ghost <at> cs.msu.su> writes:

> >> While we're at it, can somebody explain me what this 'compatibility'
> >> setting is? Is intel
> >> using its own code generator, or relays to msvc? Is it using msvc
> >> libraries of specified
> >> version? Or intel is entirely self-contained, but can emulate language
> >> and/or options of
> >> specific version of msvc?
> >>
> >
> > As far as I can tell from the link above, it
> >
> > a) has its own code generator
> > b) generates code that is ABI compatible with msvc
> > c) uses the msvc libraries
> > d) emulates msvc language/options
> 
> Thanks. So it seems like right now, intel toolset just will not work unless
cl.exe is in the
> PATH? Furthermore, I presume that to find msvc libraries (and maybe includes)
it uses environment
> variables setup by msvc scripts? Or does it use cl.exe for linking that will
therefore automatically
> uses its libraries?

The Intel xilink linker calls link, the Microsoft linker.

The Intel iclvars.bat script (also available under other names, and in
directories that vary for different releases) sets a *lot* of environmental
variables, including ones that identify where various Microsoft include and
library files are located, and where various Microsoft directories are located.
Intel's use of environmental variable is really messy, with lots of duplicate
and overlapping values.

--Beman