2017-03-17 23:32 GMT+01:00 Nicolai Hess <[email protected]>: > > > 2017-03-16 21:51 GMT+01:00 Nicolas Cellier <nicolas.cellier.aka.nice@ > gmail.com>: > >> >> >> 2017-03-15 18:14 GMT+01:00 Nicolas Cellier <nicolas.cellier.aka.nice@gmai >> l.com>: >> >>> >>> >>> 2017-03-15 15:03 GMT+01:00 Esteban Lorenzano <[email protected]>: >>> >>>> sorry for coming late to this thread… hard week :) >>>> why we are trying to compile with cygwin? >>>> is there a problem with the mingw distro? >>>> >>>> I didn’t have the time to update the README, sadly. But well… following >>>> appveyor configuration should give you all you need to reproduce the build >>>> (that’s what I did last time I built an environment). >>>> >>>> Esteban >>>> >>>> >>>> Hi Esteban, >>> How did you solve the directx problem? >>> >>> >> >> Hurrah, I succeeded in compiling Win32 Pharo VM from cygwin by using >> cross-compiler i686-w64-mingw32 >> (cygwin64 here but it could be cygwin32). >> >> This is good news, because it means that: >> - we don't have to rely anymore on non-redistributable legacy directx SDK >> - we can compile with clang if we want too (well, for all the 3rd party >> dependencies, that's a bit more work) >> - it opens the door to win64 version >> >> Some details remain: I have to pick the right libgcc and libwindpthread >> as weel as iconv.dll and copy them to the pharo build directory to satisfy >> the SDL2 dependencies. >> Maybe there's a better option for compiling SDL2 with more static stuff? >> -static-libgcc or something... >> >> cairo required another dirty hack, not the one of Igor which must be >> eliminated for cygwin compilation, but one for working around the files >> that are not truncated when overwritten... >> I wonder where this bug comes from? make? cygwin itself? VirtualBox >> (unlikely)? >> > > what hack from Igor ? I thought the pharo build just downloads a tar.gz > archive from cairo and starts the configure/build ? > >
https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/f7d3c98eaa001d2d07c1f2b75cad00fa16f86a73
