On 08/02/2016 09:34 AM, Epting, Thomas wrote:
We’re using a tool called Bullseye Coverage for measuring code coverage
with Visual Studio compilers on Windows.
When the Bullseye "integration" for Visual Studio compilers is enabled,
the installer adds one line to the end of each of the vcvarsXX.bat files
in /<vc-install-dir>//VC/bin:
@setPATH=c:/BullseyeCoverage/bin;%PATH%
The Bullseye bin folder contains a specific version of the compiler
shell (cl.exe) which does some source code preprocessing in case
Bullseye instrumentation is active at the moment. In any case the
original compiler shell from the /next/ occurrence in PATH is called to
do the actual work.
This approach is working fine with Qbs,
Are you sure that it was ever working with this particular compiler
executable? AFAIK the bat file was always looked up relative to cl.exe.
So calling setup-toolchains --detect using above PATH should have
complained in 1.5...
> but since Qbs 1.6 (as contained
in QtCreator 4.1 beta) we observe a major regression. With Bullseye
integration on (which means the PATH modification in the .bat files is
active), Qbs refuses to load the project and reports:
<...>\MsvcProbe.qbs:47: error: Error: Detecting the MSVC build
environment failed: Cannot find 'C:\BullseyeCoverage\vcvarsall.bat'.
... with this message.
Is this problem already known, is there a workaround or should I create
a Jira issue?
Please create an issue.
Christian
_______________________________________________
QBS mailing list
QBS@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qbs
