Closed jrfonseca closed 3 years ago
Big thanks Jose. Sounds like I need to give my Travis-CI bits a kick as well. I'll try to give it a look later on today/tomorrow, but in the meanwhile a small question:
Does one still need libgcc_s or friends, due to the division we use the codebase? Merely asking here - not asking you to fix it/other.
I don''t know if/why libgcc
is needed. But given we use the -static-libgcc
it should be statically linked if necessary. No further work should be necessary.
I'm going to take down https://github.com/jrfonseca/waffle . I really don't have time to pursue this longer. I pushed code to https://cgit.freedesktop.org/~jrfonseca/waffle/log/?h=appveyor for future reference.
It would be great if we could get automatic Windows builds of waffle, through AppVeyor to ensure build is always successful. https://www.appveyor.com/ is free for open-source projects and it integrates well GitHub.
This PR integrates with AppVeyor to build Waffle for 32/64 bits Windows using both MinGW and MSVC. You can see a sample build on https://ci.appveyor.com/project/jrfonseca/waffle/build/12
There are a few quirks -- see the XXX comments for details.
With an additional commit ac215785f43576e6c283699242d34b7f695479c0 one can even have AppVeyor automatically push the MSVC/MinGW binaries to Github releases, as shown in https://github.com/jrfonseca/waffle/releases/tag/appveyor-1.5.2 . But you can't just cherry-pick that commit -- if you're interested you'll need to follow the instructions https://www.appveyor.com/docs/deployment/github/ so you use a github auth token of your own for it to work.