Build on windows (with mingw) #14
Comments
|
Download all the dependencies, follow all their build instructions until you get everything compiled and end up with the required set of libraries and includes. Then point the leela-zero Makefile to the relevant directories and libs you just built in the aforementioned step, and run make (mingw) or make a MSVC console project, add the source files and set up all the library and include directories in MSVC. The latter part could be a bit easier if we'd add CMake support or so, but realistically the difficult part is the first. |
|
I am using MinGW. I managed to build all other dependencies, but it seems difficult to build OpenCL ICD loader...(I can build OpenCL ICD loader using MSVC but I want to use MinGW) |
|
That appears to be a known issue: KhronosGroup/OpenCL-ICD-Loader#11 |
|
Then how do you manage to build leelaz on windows? using MSVC? |
|
I used MSVC to build the ICD Loader. I used mingw for some other parts (IIRC getting a good performance out of OpenBLAS requires mingw, although our use is not so performance critical). Final binary can be built with MSVC or mingw, I used MSVC. |
|
when i use mingw to build leelaz, at the link step, it claims that my OpenCL.dll which was built with MSVC is "incompatible" |
|
You should be linking with the .lib (that matches the dll), not the dll itself. |
|
the same |
|
Some Googling suggests this is a common problem, there's a few proposals on the mingw wiki: See also: |
|
By the way, the issue filed against OpenCL ICD suggests that a 64-bit mingw build should work. |
|
If someone finds a way to successfully build and run on windows, it would be really great if they could provide step by step instructions in the readme. I took a crack at it, but got lost. |
There are pre-built binaries on the releases page: https://github.com/gcp/leela-zero/releases, there is no need to build the software yourself if you don't know how to do it. It is pretty complicated on Windows even if you understand what you are doing. |
|
Thanks for the pointer to the pre-built binaries. I would still like to build on windows so I can make changes and perhaps contribute. |
|
When building for Windows you cannot just build the loader by running "make", see the build instructions for the ICD loader. (The start of this thread also has some discussion that building the loader does not work with mingw, though a 64 bit build as you are doing might work anyway - I have never tried) |
|
I have created a pull request to allow building under Visual Studio. Once this is merged there shouldn't be any trouble to build on Windows. You only need to install Visual Studio 2015 Community. |
|
Thanks for adding that. I will give it a try once its merged. |
|
It almost works for me, I can build Leela itself, but autogtp fails during linking. It seems to have something to do with Qt? I have Qt 5.9.3 as well as the Qt VS Tools, and the project is configured to use the msvc2017_64 version. As far as I can tell, that's all correct. I've put curl.exe and gzip.exe from the pre-built version into the msvc folder - before it failed because it was missing them.
|
|
@odeint I will try a clean build to see if I can replicate. Meanwhile, can you try to physical clean (manually delete all output and intermediate folders and try? or this is your first build? |
|
It was a clean build. I tried now with my other computer, completely clean build, Win10 instead of 7 though. Same result, I just left the earlier stuff in this time. Which version of Qt are you using?
|
|
I've tried building with Intel C++ 17.0 instead, that gets rid of most of the warnings, but linking is still done by MSVC and fails again. [ had to follow this guide to have Boost again, "vc141" instead of "iw", https://software.intel.com/en-us/articles/intel-c-compiler-for-windows-fatal-link-error-lnk1104-when-using-intel-c-compiler-with-boost-libraries ]. The error message is only slightly more verbose in giving the name of the function call that failed:
|
|
Those warnings are normal and exists in my own build as well. The build command has been adjusted since my first build so some errors occurs here. But I have no idea about the real errors you experiencing. I have to make my own clean build when I have time tonight. Advises before I can look into it: Figure out which source file contains the functions that were missing. It might suppose to be generated by Qt though. Or more likely, they are in a cpp file that is missing in the compile. In this case, simply add that cpp file to the project will solve the problem. |
|
I can get it to compile (but probably doesn't do what it should) by commenting out these two lines in Validation.cpp: Line 167: Line 179: So it seems to be some problem with that m_results object. Edit: It actually does seem to work for normal autogtp, I guess it never needs to run the stuff from Validation.cpp - I'll just use it and see if anything's different. |
|
Yesterday I looked into it and see that Result.cpp is missing in the project. So this is why you get this error. The build command to copy curl.exe and gzip.exe also have problems. I have fixed already but the commit still have something else to fix. I am not available tonight, so wait for tomorrow. A new pull request will solve all these. The proper workaround right now, is manually add Result.cpp to the project. It should compile since then. |
|
Hey @earthengine , it is so obvious now! Didn't notice because the headers were also not in the project. Should have compared what's in the folder to whats in the MSVC project... Well that's why I'm not good at C++ ;-) Edit: And yes I periodically have to copu curl and gzip into the folder again after a rebuild or clean. Not sure how to fix that. And copy a few dlls into the final folder, too. |
|
Tried on my other machine, it also works there now. Both Visual C++ and ICC can compile. I don't see a speed difference. Let's see if there will be different results. Would it be worth it to recompile some of the dlls as well?
|
|
@odeint Because the custom action for curl.exe and gzip.exe have "Output"s to be "$(Identity)", which means they link to the same file, so the files get deleted before the action can be performed. That's my fault in the first place. To solve it, go to the property of those two exe files, click "Custom Action" in the left, then change the output from "$(Identity)" to "$(OutDir)curl.exe" or "$(OutDir)gzip.exe", according to which file are you looking at. |
Not so much recompiling but replacing OpenBLAS by MKL will help. (see config.h) |
|
@gcp Roger, did it, built it with ICC and Benchmarking now, feels maybe 20% faster than the latest stock release but I'll measure it. The libraries used are Edit: Stock gets around 3000ms per move, IntelMKL around 2350ms per move, with two concurrent autogtps running. PC is a i5-7500 and a GTX 1060 6GB. Edit2: Running only the new MKL version with -g 2 reduces it to 1075ms per move. I guess that's already summing the two instances, so comparable to 2150ms per move in the old scenario. |
|
Probably this issue can be closed now that it is possible to build on Windows using Visual Studio 2015 or 2017. |
|
closing old techsupport issue with proposed solution |
How can I build on windows?
The text was updated successfully, but these errors were encountered: