Open florianjacob opened 8 years ago
@SrTobi tried to do a compile, but stumbled over some problems. Compiling and linking needs at least his fixes from https://github.com/alacarte-maps/alacarte/tree/wintest .
The importer works, but the server throws a nullptr exception in a test, and another one on execution related to the stylesheets. He's suspecting it's somehow related to linking, and in the worst case, we have some kind of ABI problem.
@Scheirle @alex85k @Mixaill , you're the other ones related to alaCarte with access to a windows development machine, maybe you could test this as well and collaborate to find a solution? Having ready-made exe files to just download would be really awesome. đ
Also, we could integrate appveyor to accompany travis, so that we have CI building on Windows as well, to avoid such problems in the future. If somebody has or wants to get experience with appveyor? I registered the project, but I don't even know how one would compile someting on windows, so I have no idea what to write the appveyor.yml file. âšī¸
Note that I tried to compile it with Visual Studio C++, which worked (linking not so much). But I had to do some tricks with the dependencies in order to get them on windows (especially cairo). That's why I am suspecting ABI problems.
However it might be considerably easier to use mingw.
Appveyor script submitted in #92
You can use vcpkg to get MSVC-compatible libraries (something like homebrew for MacOS) http://github.com/Microsoft/vcpkg
vcpkg seems like a really good idea to lessen the pain of installing boost and cairo. :+1:
That actually seems straightforward enough we should consider adding this to the How to build-Section of the Readme as the official way to build alaCarte on Windows.
I can now confirm, that it is not an ABI problem... I get the same segmentation fault under linux (see #99). So after we solving #99 we should be able to roll out a precompiled windows version.
As there even are unofficial alacarte builds in the osm forum and seem to have quite a number of windows users (see #74 ), maybe we could provide official windows binaries via the github release binaries function?
@SrTobi, as you're the only one of us who regularily compiled on & runs Windows â can you take a look at this? Would that be possible with some build farm webservice, or cross compile on travis somehow, or would we need to build & upload the binaries for every release by hand?