All of lore.kernel.org
 help / color / mirror / Atom feed
From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/3] Adding the buildroot shell
Date: Mon, 20 Apr 2020 23:52:25 +0200	[thread overview]
Message-ID: <20200420215228.16175-1-angelo@amarulasolutions.com> (raw)

In order to simplify the usage af a buildroot sdk, this series
wants to add a buildroot shell. This shell will export all the
variables and settings needed to do crossompilation without
actually writing a buildroot package.
Is very useful in the development phase where the developer needs
to compile and check a software the most tight way.
It's similar in its working to the shell present on others build
systems.

Angelo Compagnucci (3):
  package/environment-setup: new package
  package/environment-setup: add configure alias
  package/environment-setup: add cmake alias

 docs/manual/using-buildroot-toolchain.txt     |  7 ++++
 package/Config.in                             |  1 +
 package/environment-setup/Config.in           |  6 ++++
 package/environment-setup/environment-setup   | 18 ++++++++++
 .../environment-setup/environment-setup.mk    | 34 +++++++++++++++++++
 5 files changed, 66 insertions(+)
 create mode 100644 package/environment-setup/Config.in
 create mode 100644 package/environment-setup/environment-setup
 create mode 100644 package/environment-setup/environment-setup.mk

-- 
2.17.1

             reply	other threads:[~2020-04-20 21:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 21:52 Angelo Compagnucci [this message]
2020-04-20 21:52 ` [Buildroot] [PATCH v3 1/3] package/environment-setup: new package Angelo Compagnucci
2020-04-20 21:52 ` [Buildroot] [PATCH v3 2/3] package/environment-setup: add configure alias Angelo Compagnucci
2020-04-20 21:52 ` [Buildroot] [PATCH v3 3/3] package/environment-setup: add cmake alias 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=20200420215228.16175-1-angelo@amarulasolutions.com \
    --to=angelo.compagnucci@gmail.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.