[CMake] Wrong version of cl.exe for x64
tonka tonka
tonka3100 at gmail.com
Mon Aug 22 05:22:01 EDT 2016
Does cmake call vcvarall.bat itself?
Always call vcvarall.bat before cmake itself is not really a nice solution.
Setting/override CMAKE_CXX_COMPILER to the x64 toolchain could work, but it
depends on the question “does cmake call vcvarall.bat internally“
Am 22.08.2016 10:36 schrieb "J Decker" <d3ck0r at gmail.com>:
>
>
> On Mon, Aug 22, 2016 at 1:33 AM, Nils Gladitz <nilsgladitz at gmail.com>
> wrote:
>
>> On 08/22/2016 10:28 AM, J Decker wrote:
>>
>> Maybe you need a diferent parameter to vcvarsall before running cmake
>>
>> https://msdn.microsoft.com/en-us/library/x4d2c09s.aspx
>>
>> >
>> How to: Enable a 64-Bit Visual C++ Toolset on the Command Line
>>
>>
>> To run vcvarsall.bat to use a 64-bit toolset
>>
>> 1.
>>
>> At the command prompt, change to the Visual C++ installation
>> directory. (The location depends on the system and the Visual Studio
>> installation, but a typical location is C:\Program Files (x86)\Microsoft
>> Visual Studio *version*\VC\.) For example, enter:
>>
>> To configure this Command Prompt window for 64-bit command-line builds
> that target x86 platforms, at the command prompt, enter:
> *vcvarsall amd64_x86*
>
> *shjrug* the article spells it out.
>
>>
>> The visual studio command line environments should have no effect when
>> using the visual studio generators.
>> They should only be relevant when you use one of the command line
>> generators (e.g. makefiles or ninja).
>>
>> Nils
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake/attachments/20160822/b257709d/attachment.html>
More information about the CMake
mailing list