Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Martin <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v12 0/3] Relocatable SDK: preparatory changes
Date: Mon, 17 Oct 2016 23:05:40 +0200	[thread overview]
Message-ID: <20161017210543.21573-1-s.martin49@gmail.com> (raw)

Hi all,


Here is yet another round of the series aiming improving the relocatability
of the SDK built by Buildroot.

This short series aims to clean things up about the paths used by Buildroot
by making sure the Buildroot source directory and output ones are only refered
using absolute canonical paths.

This is a prerequisite to reliably detect and fix RPATH in the SDK.

Regards,
Samuel

Samuel Martin (3):
  core: split variables definition related to in/out-of-tree build from
    O itself
  core: reorder top-level Makefile and document things
  core: re-enter make if $(CURDIR) or $(O) are not canonical paths

 Makefile | 81 ++++++++++++++++++++++++++++++++++++++++++++++------------------
 1 file changed, 59 insertions(+), 22 deletions(-)

--
2.10.0

             reply	other threads:[~2016-10-17 21:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 21:05 Samuel Martin [this message]
2016-10-17 21:05 ` [Buildroot] [PATCH v12 1/3] core: split variables definition related to in/out-of-tree build from O itself Samuel Martin
2016-10-17 21:05 ` [Buildroot] [PATCH v12 2/3] core: reorder top-level Makefile and document things Samuel Martin
2016-10-17 21:05 ` [Buildroot] [PATCH v12 3/3] core: re-enter make if $(CURDIR) or $(O) are not canonical paths Samuel Martin
2016-10-19 21:27 ` [Buildroot] [PATCH v12 0/3] Relocatable SDK: preparatory changes 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=20161017210543.21573-1-s.martin49@gmail.com \
    --to=s.martin49@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox