On Tue, Sep 20, 2016 at 11:46:23PM +0930, Daniel Burke wrote: > I do have a bit of experience with windows/linux C code interop, and while > Visual C++ tends to be somewhat... unpredictable (It's getting much better > than it used to be), I can tell you that... > > x86_64-w64-mingw32-gcc > > will output binaries that will happily run on windows, so long as you're > using a version at least as new as is provided with Debian Jessie. (the > wheezy version produced broken binaries). Wine can then be used to test > them quite reliably. That compiler comes with enough windows libraries and > headers to do most reasonable jobs, and quite a few unix headers mangled to > work in windows environments. > > sudo apt-get install mingw-w64 > > There's a 32bit version if you're that way inclined (which is also broken > on wheezy), although I haven't used it recently enough to recall it.
Thanks for the info. We should try to get some mingw builds and wine tests into Travis (although at the moment the Travis builds are already broken due to a problem on clang I haven't had a chance to debug :). However, as noted elsewhere, mingw shouldn't be our only or primary way of building for windows. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson
Description: PGP signature
_______________________________________________ ccan mailing list firstname.lastname@example.org https://lists.ozlabs.org/listinfo/ccan