All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/environment-setup: new package
Date: Tue, 3 Nov 2020 22:45:06 +0100	[thread overview]
Message-ID: <20201103224506.33dcba07@windsurf.home> (raw)
In-Reply-To: <20201027140140.47982-1-matthew.weber@rockwellcollins.com>

Hello,

On Tue, 27 Oct 2020 09:01:40 -0500
Matt Weber <matthew.weber@rockwellcollins.com> wrote:

> From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
> 
> Install an helper script to setup a build environment based on buildroot.
> It's useful when a developer wants to use a buildroot generated sdk to
> build an external project.
> 
> Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
> Tested-by: Michael Trimarchi <michael@amarulasolutions.com>
> Tested-by: Adam Duskett <aduskett@gmail.com>
> Signed-off-by: Maury Anderson <maury.anderson@collins.com>
> Signed-off-by: Matt Weber <matthew.weber@rockwellcollins.com>
> ---

I've applied to master, with a number of small changes. The main is
probably getting rid of the "buildroot shell" terminology. There's no
such thing as a "buildroot shell". There's a script that exports a
number of environment variables and aliases in your current shell.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2020-11-03 21:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27 14:01 [Buildroot] [PATCH] package/environment-setup: new package Matt Weber
2020-10-27 15:56 ` Angelo Compagnucci
2020-11-03 21:45 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-04-18 10:31 Angelo Compagnucci
2020-04-18 12:45 ` Yann E. MORIN
2020-04-18 12:54   ` Thomas Petazzoni
2020-04-18 13:26   ` Angelo Compagnucci

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=20201103224506.33dcba07@windsurf.home \
    --to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.