From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH][autobuild] autobuild-run: introduce "--tc-cfg-uri" option for toolchain configs URI
Date: Fri, 21 Oct 2016 13:34:52 +0200 [thread overview]
Message-ID: <20161021133452.0508e5c5@free-electrons.com> (raw)
In-Reply-To: <1477045454-8660-1-git-send-email-vzakhar@synopsys.com>
Hello,
On Fri, 21 Oct 2016 13:24:14 +0300, Vlad Zakharov wrote:
> This commit introduces "--tc-cfg-uri" option (short "-t").
> Described option is used to pass URI of file that contain
> toolchains configurations to be used in autobuilds.
>
> Default value refers to standard buildroot autobuild toolchain
> configuration file:
> http://autobuild.buildroot.org/toolchains/configs/toolchain-configs.csv
>
> Such update allows users to add their own toolchain configurations
> to use in buildroot autobuilds.
>
> Signed-off-by: Vlad Zakharov <vzakhar@synopsys.com>
I am not sure I like this approach very much. It means people can start
using a non-default set of toolchains, and then submit results to
autobuild.buildroot.org. Such results would possibly not be
reproducible by others because we may not have access to those
toolchains.
Is this intended to run tests only the ARC architecture builds on your
autobuilder?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-21 11:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 10:24 [Buildroot] [PATCH][autobuild] autobuild-run: introduce "--tc-cfg-uri" option for toolchain configs URI Vlad Zakharov
2016-10-21 11:34 ` Thomas Petazzoni [this message]
2016-10-21 11:56 ` Vlad Zakharov
2016-10-21 12:04 ` Alexey Brodkin
2016-10-21 18:13 ` Arnout Vandecappelle
2016-10-21 19:18 ` Alexey Brodkin
2016-10-21 19:28 ` Arnout Vandecappelle
2016-10-21 19:44 ` Alexey Brodkin
2017-02-06 17:58 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161021133452.0508e5c5@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox