|Re: [hatari-devel] Building Hatari 2.xx on Windows platform (?)|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Building Hatari 2.xx on Windows platform (?)
- From: Douglas Little <doug694@xxxxxxxxxxxxxx>
- Date: Tue, 27 Jun 2017 14:26:27 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=5b2y7z3YrZtLZvhufU5YOw8ZX8FTzED6Pzh+pLN3rM0=; b=HLl39+t0oVsnwEqtfx9J4us8RYFaHe5tDtg8W9PpPmfasnO89RehW59lXbd+tdydhQ /eyf//Arnl0NMgSpEfEigbrSOJ2jXUl3RMDpkX9YwBj2C4Az0sokIgVdNqqRuZUv5Upy Yid+wjRPIEwoJlnMy0HlOBUWlq/Vf/erClRdxM4QC0nX8RkYKs1baZla44MYoBbUrmyy bFg9Olq0JgcHsNy95oIJccCQJLFoOsVgXvNvU3P9QeS2mqZ0BSL8cqr8TdWxksL8no9X FXrZdOMn4QlD/zy4Hs3EJgCX1pTq3VGF+dRplsQ60gIVSruIzNxtKFBkFQ26I4/HZ7zf 920w==
My attempt using mingw was to build from its own msys shell (i.e. not using cygwin at all). This results in lots of problems detecting and configuring stuff - I ended up overriding lots of the cmake vars to get it past the first collection of path and environmental errors and then gave up as I slowly realised this was 'not the right way' to build Hatari :).
It did manage to produce some .vcxproj files from that process, which I played with - but the code would not build under VC for (what looked like) dialect reasons. e.g.. from the. 'inline' keyword and missing stdint.h or unistd.h. Some compiled ok as C++ but again - I decided to stop there!
I didn't try configuring to cross-compile with mingw from cygwin.. Didn't even consider that.