tag:help.appveyor.com,2012-11-13:/discussions/problems/16439-how-to-use-64bit-version-of-clexe-for-buildAppVeyor: Discussion 2019-06-27T05:24:11Ztag:help.appveyor.com,2012-11-13:Comment/460259212018-09-05T08:00:23Z2018-09-05T08:00:23ZHow to use 64bit version of cl.exe for build?<div><p>You need to call <code>vcvars64.bat</code> as described <a href="https://www.appveyor.com/docs/lang/cpp/#visual-studio-2017">here</a>.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/460259212018-09-05T19:39:51Z2018-09-05T19:48:25ZHow to use 64bit version of cl.exe for build?<div><p>This should be called in the <code>init</code> step of the yaml file for anyone else looking for the solution and thank you for the above response.</p></div>anmoltag:help.appveyor.com,2012-11-13:Comment/460259212018-09-05T22:21:04Z2018-09-05T22:21:04ZHow to use 64bit version of cl.exe for build?<div><p>This still doesn't seem to solve the issue.</p>
<p>C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\cl.exe /c /nologo /Ox s (x86)\Windows Kits\NETFXSDK\4.6.1\include\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.14393.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.14393.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.14393.0\winrt" "-IC:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE" "-IC:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ATLMFC\INCLUDE" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.14393.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\include\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.14393.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.14393.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.14393.0\winrt" "-Ic:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\INCLUDE" "-IC:\Program Files\Microsoft SDKs\Windows\v7.1\INCLUDE" "-IC:\Program Files\Microsoft SDKs\Windows\v7.1\INCLUDE\gl" /EHsc /Tpc\capi.cc /Fobuild\temp.win32-3.5\Release\c\capi.obj<br>
capi.cc</p>
<pre>
<code>c:\users\appveyor\appdata\local\temp\1\pip-req-build-kllf80pc\c\python/list.h(33): error C2034: 'py::olist::<alignment member>': type of bit field too small for number of bits
error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\cl.exe' failed with exit status</code>
</pre></div>anmoltag:help.appveyor.com,2012-11-13:Comment/460259212018-09-06T00:14:26Z2018-09-06T00:14:26ZHow to use 64bit version of cl.exe for build?<div><p>Can you please link to a specific build.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/460259212018-09-06T00:17:22Z2018-09-06T00:17:22ZHow to use 64bit version of cl.exe for build?<div><p>Yes here is a link: <a href="https://ci.appveyor.com/project/h2oops/datatable/build/0.4.155/job/dffg40x5j7roymrb">https://ci.appveyor.com/project/h2oops/datatable/build/0.4.155/job/...</a></p></div>anmoltag:help.appveyor.com,2012-11-13:Comment/460259212018-09-06T16:45:51Z2018-09-06T16:45:51ZHow to use 64bit version of cl.exe for build?<div><p>Have you tried a build on <em>Visual Studio 2017</em> image as per your initial post?</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/460259212018-09-06T18:41:59Z2018-09-06T18:41:59ZHow to use 64bit version of cl.exe for build?<div><p>It seems to still force the use of VS 14 as seen here near the end of the build, the start however does initialize with VS 2017.</p>
<p><a href="https://ci.appveyor.com/project/h2oops/datatable/build/0.4.159/job/n0guhm1tnwo5aq35">https://ci.appveyor.com/project/h2oops/datatable/build/0.4.159/job/...</a></p></div>anmoltag:help.appveyor.com,2012-11-13:Comment/460259212018-09-12T03:19:37Z2018-09-12T03:19:37ZHow to use 64bit version of cl.exe for build?<div><p>I admit i'm far from an expert on python build process (setup.py etc.) so can you explain <a href="https://github.com/h2oai/datatable/commit/308ed5cba22f07661e4dc016781090e0703cd2f8">this commit</a> to me. I could be wrong but just by name alone, it looks significant.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/460259212018-09-13T18:42:38Z2018-09-13T18:42:38ZHow to use 64bit version of cl.exe for build?<div><p>I tried changing the syntax to use win64 as something that may resolve the issue with the builds running on Windows based systems; but further research showed that win32 is sufficient even when dealing with x64 systems and this did not change any of the results.</p></div>anmoltag:help.appveyor.com,2012-11-13:Comment/460259212018-09-18T22:19:38Z2018-09-18T22:19:38ZHow to use 64bit version of cl.exe for build?<div><p>I noticed that it uses a different version of <code>cl.exe</code> (i.e. the vs2017 one) on your <strong>python 3.6</strong> build. I also noticed (in my own fork) that if I have set the <code>vcvars</code> and then I call <code>- where cl.exe</code> just before the command that results in error, it still points to the visual studio 2017 version.<br>
Do those facts bring anything to mind?</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/460259212018-09-20T22:01:54Z2018-09-20T22:16:02ZHow to use 64bit version of cl.exe for build?<div><p>I've noticed this as well, VS 2017 does not seem to be used, I'll set <code>- where cl.exe</code> to see where it points to.</p>
<p><a href="https://ci.appveyor.com/project/h2oops/datatable/build/0.4.160/job/tsyc06suwlms18rb#L194">https://ci.appveyor.com/project/h2oops/datatable/build/0.4.160/job/...</a></p>
<p>It says VS 2017 when I ask - where, but later in the build is shows it still uses VS 2014 instead.</p></div>anmol