On Wed, Jul 08, 2015 at 09:02:10PM +0200, Laszlo Ersek wrote: > My lack of faith is based on "experience" :) We've been complaining > about this for ages on the list. I think it is safe to assume that the > primary "participant" that has legal access to all supported Microsoft > toolchains is Intel. As described (and provided!) by Scott, > gcc-for-Windows is almost trivially available (all supported gcc > versions). It seems to follow that Intel should operate such a build > farm. Based on how long we've been whining about this, I don't think > it's going to happen any time soon.
Since I had a few days off from the daily grind, I setup Jenkins and a few VMs to build edk2 trunk, polling svn for changes. At the moment it builds debug and release, 32-bit and 64-bit OVMF on Linux gcc 4.6, 4.7, 4.8, 4.9 and 5.1, and MSVC 2008, 2010, 2012 and 2013. gcc 4.4 and 4.5 need more investigation since the compilers don't build. The Jenkins URL to see build status etc. is https://edk2.bluestop.org:8000/jenkins . I've also set up an EDKSMOKE repository at https://edk2.bluestop.org/diffusion/EDKSMOKE which currently lets anyone with an account push changesets to. I've not done the integration yet, but the idea is that I'll hook it into Jenkins to let people smoke test changesets on the various configurations I'll setup. -- Bruce ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
