From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] Makefile: use absolute paths to BR2_EXTERNAL
Date: Sun, 2 Feb 2014 11:23:49 +0100 [thread overview]
Message-ID: <20140202102349.GC3331@free.fr> (raw)
In-Reply-To: <52E696A9.5070700@mind.be>
Arnoud, All,
On 2014-01-27 18:26 +0100, Arnout Vandecappelle spake thusly:
> On 22/01/14 21:59, Yann E. MORIN wrote:
> >+ _BR2_EXTERNAL = $(shell cd $(BR2_EXTERNAL) >/dev/null 2>&1 && pwd)
> >+ ifeq ($(_BR2_EXTERNAL),)
> >+ ifeq ($(patsubst /%,/,$(BR2_EXTERNAL)),/)
> >+ $(error BR2_EXTERNAL='$(BR2_EXTERNAL)' does not exist)
> >+ else
> >+ $(error BR2_EXTERNAL='$(BR2_EXTERNAL)' does not exist, relatively to $(TOPDIR))
>
> I don't think the limited explanation "relatively to $(TOPDIR)" warrants
> the additional complexity of patsubsting stuff.
Well, we want to tell the user why w edid not find his BR2_EXTERNAL.
And since it can be tricky to understand that a relative path is not
found, we do want to highlight that fact in the error message.
> >+ endif
> >+ endif
> >+ BR2_EXTERNAL := $(_BR2_EXTERNAL)
>
> AFAICS there is no need to have a separate _BR2_EXTERNAL, since we'll
> anyway error out if it is empty.
I used an intermediate, since I want to display the user-supplied path
in the error message, not the one we found (or did not find).
> So, I'd propose:
>
> override BR2_EXTERNAL := $(shell cd $(BR2_EXTERNAL) >/dev/null 2>&1 && pwd)
> ifeq ($(BR2_EXTERNAL),)
> $(error BR2_EXTERNAL directory '$(BR2_EXTERNAL)' does not exist)
> endif
Uh? In this case $(BR2_EXTERNAL) would be empty in the error message, no?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-02-02 10:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 20:59 [Buildroot] [PATCH 0/3] BR2_EXTERNAL, O: misc fixes and docs Yann E. MORIN
2014-01-22 20:59 ` [Buildroot] [PATCH 1/3] Makefile: use absolute paths to BR2_EXTERNAL Yann E. MORIN
2014-01-22 21:22 ` Samuel Martin
2014-01-23 8:48 ` Jeremy Rosen
2014-01-26 13:53 ` Thomas Petazzoni
2014-01-27 17:18 ` Arnout Vandecappelle
2014-02-02 10:19 ` Yann E. MORIN
2014-02-02 10:16 ` Yann E. MORIN
2014-01-27 17:26 ` Arnout Vandecappelle
2014-02-02 10:23 ` Yann E. MORIN [this message]
2014-02-02 11:01 ` Arnout Vandecappelle
2014-02-02 11:09 ` Yann E. MORIN
2014-01-22 20:59 ` [Buildroot] [PATCH 2/3] manual: $(BR2_EXTERNAL)/{Config.in, external.mk} are mandatory Yann E. MORIN
2014-01-22 21:18 ` Samuel Martin
2014-01-22 20:59 ` [Buildroot] [PATCH 3/3] manual: add explanations on limitation about using O= Yann E. MORIN
2014-01-22 21:18 ` Samuel Martin
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=20140202102349.GC3331@free.fr \
--to=yann.morin.1998@free.fr \
--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