On Wed, Oct 21, 2015 at 7:31 PM, Nick Wellnhofer <wellnho...@aevum.de> wrote:
> On 21/10/2015 09:11, David Drysdale wrote: > >> On Fri, Oct 16, 2015 at 2:41 PM, Daniel Veillard <veill...@redhat.com> >> wrote: >> >>> The biggest issue I have is non-linux, I never use Windows or Macs >>> and I have zero clue that a change there could break the build or else. >>> There are mingw builds of libxml2 done within Red Hat but that's not >>> real Windows tests. >>> >> >> The Travis builds do at least add OSX testing, which was fairly >> straightforward to set up (I disabled the EBCDIC test file because >> the iconv() on OSX doesn't include EBCDIC support). >> >> I imagine a Windows build would a lot more effort to get automated, >> if/when Travis add support for it... >> > > The Windows build could be tested with Appveyor. They offer free CI > services for open-source projects. Setup is similar to Travis. > Thanks for the pointer -- I've added an AppVeyor build to my clone of the repo: https://ci.appveyor.com/project/daviddrysdale/libxml2 > Nick > > > _______________________________________________ > xml mailing list, project page http://xmlsoft.org/ > xml@gnome.org > https://mail.gnome.org/mailman/listinfo/xml >
_______________________________________________ xml mailing list, project page http://xmlsoft.org/ xml@gnome.org https://mail.gnome.org/mailman/listinfo/xml
