On Tue, 2020-04-14 at 10:54 +0100, Daniel P. Berrangé wrote: > On Fri, Apr 10, 2020 at 11:10:33AM +0200, Andrea Bolognani wrote: > > The xcode10.3 build has recently started failing because of issues > > that are not in libvirt, so get rid of it. It didn't buy us > > additionaly platform coverage anyway, since underneath it's using > > the same macOS 10.14 version as xcode11.3. > > The point was to test both xcode versions, since they're both commonly > used. I was testing this over the weekend and determined that 10.1 > will still work correctly. Travis broke something in their 10.2/10.3 > images that inserts a bogus -I path. Considering that almost nobody in the libvirt community is actually focused on macOS support, trying to chase after two SDKs instead of a single one doesn't necessarily sound like a good idea to me, especially when the older one doesn't target the current version of macOS. It's already pretty bad that we're stuck on 10.14, as opposed to 10.15 which is the version we actually target according to our platform support policy, because Travis CI always takes forever to prepare new images. I was looking into Cirrus CI the other day and they support macOS too, and they even already have a 10.15 image. I didn't dig deeper, but maybe if we're stuck using an external service for macOS builds it should be Cirrus CI instead of Travis CI. -- Andrea Bolognani / Red Hat / Virtualization
