[haiku-development] Re: Haiku build continuous intergration server

  • From: Ingo Weinhold <ingo_weinhold@xxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Mon, 23 Sep 2013 11:22:47 +0200

On 09/23/2013 07:01 AM, Alexander von Gluck wrote:
On Sun, 2013-09-22 at 21:50 -0700, Urias McCullough wrote:
On Sun, Sep 22, 2013 at 9:34 PM, Urias McCullough <umccullough@xxxxxxxxx> wrote:
Lets say something changes in haiku that would affect the buildtools
generation... the process breaks down at that point as buildbot, bamboo,
etc, isn't aware of the need to rebuild the buildtools..

Unless you're rebuilding the buildtools every time the haiku repo
changes, then this problem won't get solved anyway.

Ah.. good point. Didn't think of it in that direction.

Maybe we should "cheat" and just blow away the buildtools every night
to force a fresh copy to be built daily regardless.

That would mean that at worst, our CI mechanism would use a stale
buildtools for 24 hours before repairing itself. Of course, the
ability to manually blow away the broken buildtools if it did failed
would always be nice. (I've done that on occasion for my buildslaves
to get them back on track again).

Eh. Fair enough.  24 hours may even be a little much. maybe rebuild the
buildtools weekly (and on buildtools commits)

ATM the gcc build only depends on the scripts configure and build_cross_tools[_gcc4], and a subset of our public headers (config, posix, os (of those probably only os/support and os/kernel)). So it should suffice to check whether any of these have changed.

Is it a bug in "our" buildtools? Or in gcc2 in general? GCC2 wasn't
exactly the pinnacle of clean FOSS ;)

Oh, it's definitely a bug in gcc2... they both operate differently in
determining library and program paths. (gcc3+ can generally "figure it
out")

At any rate there's simply no reason to move gcc 2. Just generate it somewhere and leave it there. That doesn't even imply that you have to build Haiku in the same generated directory; you can keep them separate, if you want.

CU, Ingo


Other related posts: