On Fri, 21 Mar, at 11:46:53AM, Laszlo Ersek wrote: > > Do you build each one of your patches with sixteen (compiler, target > arch) pairs during live development? Increasing the latency of your > build cycle from like 1 minute to a quarter of an hour? And that's > supposing that you can fire off each gcc version and each MSVC version > in an automated, scripted manner, without human intervention.
This is a valid point, and one that has bitten me recently (repeatedly). The usual solution to this problem is some kind of buildbot or continuous integration infrastructure for the project. Doing development across multiple OSes and toolchains is hard. Doing it manually is near impossible, which is why most projects automate it. Automation also reduces the latency between the time you make the change and the time you find out about any errors, which is critical in avoiding the problem of having to drop everything to fix patches you wrote weeks/months ago. Has anyone ever looked at setting up something like this before? -- Matt Fleming, Intel Open Source Technology Center ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel