- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Currently we are using build services toochain which builds our software. It has multiple versions of Visual Studio Versions from 6.0 to 9.0 I am trying to integrate the Intel C++ compiler into the toolchain. I was able to integrate the compiler by calling icl.exe from the installed distributions of Intel. However when I tried to link, using xilink.exe, I get a very unusual error which is :
LINK : fatal error LNK1181: cannot open input file '/nologo.obj'
As you see the special characters before /nologo is being inserted. But the major issue is that xilink is calling 7.0 MSVC linker . I am not sure if xilink requires MSVC linker but this is what I sw in the commnd line hwihc is as follows:
-----------------------------------------------------------
xilink: executing 'link'
Microsoft (R) Incremental Linker Version 7.10.3077
Copyright (C) Microsoft Corporation. All rights reserved.
/nologo
/verbose
/VERSION:12.1
/OPT:REF
/IGNORE:4089
---------------------------------------------------------------
Is it possible to override the MSVC version that xilink selects from 7.0 to 9.0 without chainging environment variables? I want to check if switching to MSVC 9.0 solves the issue of special character.
I want to keep modifying environment variable as the last option since it will disrupt lots of existing stuff.
Thanks much.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
TimP (Intel) wrote:Thanks for option. I have to explicitly call xilink.exe and not icl.exe (which is invoked before xilink.exe). When I provided the -Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\AMD64" as a command line parameter to Xilink.exe, I get this warning xilink: warning #10006: ignoring unknown option '-Qlocation,link,C:\Program Files ... ' On Windows I tried with both /QLocation as well as -QLocation fomats. Is there something that I am missing here?The option /Qlocation allows setting a specific version of Microsoft tools, e.g.
-Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\AMD64"
This can be set in icl.cfg or in command line options.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page