Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Vianney_PHILIPPE
New Contributor I
167 Views

xilink always forcing rebuild (change in the command line)

Jump to solution

Hello,

I am using Intel Composer XE SP1 Update 4 for Windows.
To compile my project, I use :

call "%VS110COMNTOOLS%vsvars32.bat"
msbuild /v:d /p:VisualStudioVersion=11.0;Configuration=Release Marvel.Maths.AvxCalculationNativeKernels.vcxproj

With this setup, if I run msbuild command again, xilink is called :

  All outputs are up-to-date.
  Forcing rebuild of all source files due to a change in the command line since the last build.
  Forcing rebuild of all source files due to a change in the command line since the last build.

(full detailed log is attached)
I cannot find any difference between both command lines (starting from the /OUT parameter)

Why is xilink rebuiling my project?

Thanks in advance for your help

Vianney

0 Kudos
1 Solution
Vianney_PHILIPPE
New Contributor I
167 Views

Removed erroneous comment.

View solution in original post

10 Replies
MalReddy_Y_Intel
Employee
167 Views

Hi,

Would it be possible to share the project files to investigate further ?

Thanks,

Reddy

 

Vianney_PHILIPPE
New Contributor I
167 Views

Hello Reddy,

I have attached a minimalist project that reproduces the problem.
To proceed, just run :

Marvel\Maths\AvxCalculationNativeKernels\build.cmd

The batch will :

  • Rebuild from scratch
  • Build incrementally with details and save the build log
  • Grep for "change in the command line" in the build.log.

You will also find the log generated on my desktop in Marvel\Maths\AvxCalculationNativeKernels\msbuild.log.

Regards,

Vianney

Vianney_PHILIPPE
New Contributor I
167 Views

One of my colleague just tested my demo project with XE 2015, and we still have the same rebuild problem.
We also checked that the log has a line saying "Building with Intel(R) C++ Compiler XE 15.0".

MalReddy_Y_Intel
Employee
167 Views

Thanks for sharing the demo project, I will investigate and update you.

Reddy

 

MalReddy_Y_Intel
Employee
167 Views

Hi,

I suspect the difference of quotes for xilink.exe in the first command and tracker command might be causing the issue. However this issue is escalated to engineering team, I will check status and keep update you.

Thanks,

Reddy

 

Vianney_PHILIPPE
New Contributor I
167 Views

Thanks Reddy, waiting for your feedback.

Vianney_PHILIPPE
New Contributor I
167 Views

[3rd version of this comment]

Hello,

If I update my ard.ProjectCompileOptions.props file to force BasePlatformToolset :

<PlatformToolset Condition="'$(VisualVersion)' == 'vc9'">v90</PlatformToolset>
<PlatformToolset Condition="'$(VisualVersion)' == 'vc10'">v100</PlatformToolset>
<!-- Fix begin -->
<BasePlatformToolset Condition="'$(UseIntelCppCompiler)' == 'true'">$(PlatformToolset)</BasePlatformToolset>
<!-- Fix end -->
<PlatformToolset Condition="'$(UseIntelCppCompiler)' == 'true'">Intel C++ Compiler XE 14.0</PlatformToolset>

The compiler complains about a missing target :

C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Platforms\Win32\PlatformToolsets\Intel C++ Compiler XE 14.0\Microsoft.Cpp.Win32.Intel C++ Compiler XE 14.0.targets(1172,7): error MSB4057: The target "ComputeLegacyManifestEmbedding" does not exist in the project.

If I add this target in my project :

<Target Name="ComputeLegacyManifestEmbedding" Condition="'$(BasePlatformToolset)' == 'v100'" />

It now works in x86 (no more rebuild).

Unfortunately, it fails in x64 (tracker event missing) :

TRACKER : error TRK0002: Failed to execute command: ""C:\Program Files (x86)\Intel\Composer XE 2013 SP1\bin\Intel64\xilink.exe" @C:\Users\vphilipp061807\AppData\Local\Temp\tmp889edd048c194b4b85d99ee8bd51764a.rsp". The operation identifier is not valid.

Vianney

Vianney_PHILIPPE
New Contributor I
167 Views

I'm back from holidays. Any update on this?

Vianney_PHILIPPE
New Contributor I
168 Views

Removed erroneous comment.

View solution in original post

MalReddy_Y_Intel
Employee
167 Views

Dear Customer,
FYI. This issue should have been fixed and Please verify with v15.0 update 3 release which is available at https://registrationcenter.intel.com/.

Thanks,

Reddy

 

Reply