On 02/29/2016 09:16 AM, Yedidyah Bar David wrote: > On Mon, Feb 29, 2016 at 3:00 PM, Christophe Fergeau <cfergeau@xxxxxxxxxx> wrote: >> On Thu, Feb 18, 2016 at 01:51:25PM -0500, Cole Robinson wrote: >>> On 02/18/2016 12:51 PM, Roman Kagan wrote: >>>> On Wed, Feb 17, 2016 at 06:11:54PM -0500, Cole Robinson wrote: >>>>> On 02/08/2016 11:07 AM, Roman Kagan wrote: >>>>>> On Mon, Feb 08, 2016 at 12:35:21PM +0100, Christophe Fergeau wrote: >>>>>>> For what it's worth, I've had success building (did not test) qemu-ga >>>>>>> with mingw using the attached spec file. >>>>>> >>>>>> We build it in a similar way and use it in our testing for some time. >>>>>> >>>>>> Are you planning to split it out of virtio-win somehow? >>>>>> >>>>> >>>>> I think Christophe was experimenting with building qemu-ga for integration >>>>> into spice-guest-tools.exe >>>> >>>> I must admit I didn't know about spice-guest-tools.exe. AFAICS from >>>> http://www.spice-space.org/download.html it's yet another means to bring >>>> the stuff from virtio-win into the guest, is it? If so how is it synced >>>> with virtio-win? >>>> >>> >>> Yes that's one of the things we have discussed getting on the .iso at some >>> point, or doing nightly builds. Right now I think Christophe just builds it >>> manually on occasion, I don't think it's automated. The build code is here: >>> >>> https://cgit.freedesktop.org/~teuf/spice-nsis/ >> >> Didi (cc'ed) has been doing some great work in automating this as they >> wanted to use this (+ their ovirt agent) for oVirt guests. Current >> upstream repository is >> https://cgit.freedesktop.org/spice/spice-nsis/ > > In ovirt we have this manually-synced at: > > https://gerrit.ovirt.org/gitweb?p=ovirt-wgt.git;a=summary > > See this if you want to work with this gerrit instance: > > http://www.ovirt.org/develop/dev-process/working-with-gerrit/ > > "manually" means that we sometimes do reviews there, but only actually > merge patches after they were merged in spice-nsis, with same commit > hashes. > >> >> There now is a Makefile extracting the drivers we need from the >> virtio-win ISO, which means going through a few steps we'd rather avoid: >> https://cgit.freedesktop.org/spice/spice-nsis/tree/Makefile#n106 > > See also: https://bugzilla.redhat.com/show_bug.cgi?id=1167941 > >> >> Then we have a .spec file which can generate the installer from a >> virtio-win rpm, vdagent rpm, qxl rpm. >> >> In other words, the whole build process of spice-nsis is now much more >> saner and automatable/automated. Not having to extract the files >> manually from virtio-win.iso would indeed be even better, and making >> all these bits of pieces (mingw-vdagent, an installer, ..) available >> from a single place would indeed be even better. >> >> Christophe > > Thanks to Sandro's recent work, jenkins builds are fully automated > now. E.g., we recently posted this to spice-devel: > > https://lists.freedesktop.org/archives/spice-devel/2016-February/026436.html > > We also pushed it to gerrit: > > https://gerrit.ovirt.org/53326 > > At the bottom you can see links to jenkins builds inside the comments. > > I do not think I am subscribed to virt-tools-list, sorry. > Thanks for the info! (just responding so this shows up in virt-tools-list archives for posterity) - Cole _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
