Hi Justin, Sunil, On 5/20/20 12:26 PM, Philippe Mathieu-Daudé wrote: > +launchpad ticket > > On 9/20/19 6:53 PM, Justin Terry (VM) wrote: >> Hey Phil, >> >> I have contacted our legal department for guidance on this specific >> use case and will update you when I hear back. Thank you for your >> patience.
I recently understood legal changes can be very complex, thus it is implicit it can take years before getting updates. Since the project is still actively developed, maybe you could provide a Azure CI job to build a WHPX binary. We don't need to have access to the binary, just to the exit status (success/fail) and build logs. Do you think it is doable? Thanks, Phil. >> >> Justin Terry >> >>> -----Original Message----- >>> From: Philippe Mathieu-Daudé <phi...@redhat.com> >>> Sent: Friday, September 20, 2019 8:18 AM >>> To: qemu-devel@nongnu.org; Justin Terry (VM) <jute...@microsoft.com> >>> Cc: Daniel P . Berrangé <berra...@redhat.com>; Fam Zheng >>> <f...@euphon.net>; Thomas Huth <th...@redhat.com>; Paolo Bonzini >>> <pbonz...@redhat.com>; Alex Bennée <alex.ben...@linaro.org>; Richard >>> Henderson <r...@twiddle.net>; Eduardo Habkost <ehabk...@redhat.com>; >>> Stefan Weil <s...@weilnetz.de> >>> Subject: Re: [PATCH v2 0/3] testing: Build WHPX enabled binaries >>> >>> On 9/20/19 1:33 PM, Philippe Mathieu-Daudé wrote: >>>> Add a job to cross-build QEMU with WHPX enabled. >>>> >>>> Since the WHPX is currently broken, include the patch required to have >>>> successful Shippable build. >>>> >>>> I previously included the WHPX headers shared by the Android project, >>>> and Daniel asked me to check the EULA. While trying to manually >>>> install the Windows SDK, I noticed the installer fetches archives >>>> directly, kindly asking where they are stored via the /fwlink API. >>>> Do the same, fetch the required archives and extract them. No need to >>>> accept EULA... >>>> >>>> Docker build the image first, then build QEMU in a instance of this >>>> image. The image is internal to Shippable, the instances are not >>>> reachable and are thrown once the build is finished. What we collect >>>> from Shippable is the console output of QEMU build process, and if the >>>> build process succeed or failed. So far we do not redistribute the >>>> image or built binaries. >>>> >>>> Philippe Mathieu-Daudé (3): >>>> target/i386: Fix broken build with WHPX enabled >>>> tests/docker: Add fedora-win10sdk-cross image >>>> .shippable.yml: Build WHPX enabled binaries >>> >>> FWIW here is the result of this series: >>> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapp. >>> shippable.com%2Fgithub%2Fphilmd%2Fqemu%2Fruns%2F516%2F11%2Fcon >>> sole&data=02%7C01%7Cjuterry%40microsoft.com%7C733a566f3233427 >>> 8ae6f08d73dddb39f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6 >>> 37045894733463150&sdata=55URgDII5r74QMUpLOD%2FWT5%2B5jbzyv >>> nfCSdv%2FNaWDAw%3D&reserved=0 >>> Duration 17 minutes (1076 seconds) >>> >>> 4m49s building the qemu:fedora-win10sdk-cross docker image, 11m10s >>> building WHPX QEMU. >
