[RFC] Refactor autoconf options and build scripts

Jean-Marie Lemetayer jeanmarie.lemetayer@gmail.com
Tue Sep 15 14:21:00 GMT 2015


To continue the Jasmin work about Travis-CI, I have copy paste the
Jasmin `.travis.yml` on my fork and add a script line to build all
samples this way:

    for SAMPLE in $(./ct-ng list-samples 2>/dev/null | sed -n
's/^\[...\] *\(.*\)$/\1/p'); do ./ct-ng $SAMPLE; ./ct-ng build; done

It seems to be working for now: https://travis-ci.org/jmlemetayer/crosstool-ng

But going further into the Travis-CI documentation I see that the
build timeouts after 50 minutes:

So it seems not to be the good strategy as building all samples
serially will take more than 50 minutes. But we could run parallel
builds using matrix build:

The only difference is that we can't run build dynamically (using
`list-samples`) and we have to say which samples we want to build for
the continuous integration.

So, I think it could be a good thing to test / refresh the whole
samples and add them into the parallel integration builds when ready.


2015-09-14 2:31 GMT+02:00 Jasmin J. <jasmin@anw.at>:
> Hi!
>> I will give it a try, when I have time this week.
> Well, I was too curious to sleep ... ;)
> Here the result of the first ct-ng test build:
>   https://travis-ci.org/jasmin-j/crosstool-ng/builds/80157690
> Here is the source for travis-ci:
>   https://github.com/jasmin-j/crosstool-ng/tree/add_travis_ci
>> Maybe someone is so pleasant to tell me which binutils/gcc/libc(newlib)/gdb
>> combinations I shall try as a first step.
> What shall I try?
> BR
>    Jasmin
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq

For unsubscribe information see http://sourceware.org/lists.html#faq

More information about the crossgcc mailing list