From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] manual: switch BR2_EXTERNAL examples to use absolute paths
Date: Sat, 22 Feb 2014 21:45:43 +0100 [thread overview]
Message-ID: <87ppmeswp4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <48973489-6ffd-4d9d-b8ad-0d9392ebe929@email.android.com> (Thomas De Schampheleire's message of "Sat, 22 Feb 2014 13:09:39 +0100")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:
> "Yann E. MORIN" <yann.morin.1998@free.fr> schreef:
>> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
>>
>> Although it is possible to use relative paths, there are a few pitfalls
>> whith doing so.
> With, but actually I think when would be better.
..
>> -The +BR2_EXTERNAL+ path can be either an absolute or a relative path,
>> +*Note:* the +BR2_EXTERNAL+ path can be either an absolute or a relative path,
>> but if it's passed as a relative path, it is important to note that it
>> -is interpreted relatively to the main Buildroot source directory, not
>> +is interpreted relatively to the main Buildroot source directory, *not*
> I may be wrong, but I also think it should be 'relative' here...
I think so too. Committed with that fixed, thanks both.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-02-22 20:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 22:17 [Buildroot] [PATCH 0/3 v3] BR2_EXTERNAL, O: misc fixes and docs Yann E. MORIN
2014-02-21 22:17 ` [Buildroot] [PATCH 1/3] Makefile: internally use absolute paths to BR2_EXTERNAL Yann E. MORIN
2014-02-22 12:06 ` Thomas De Schampheleire
2014-02-22 20:40 ` Peter Korsgaard
2014-02-21 22:17 ` [Buildroot] [PATCH 2/3] manual: switch BR2_EXTERNAL examples to use absolute paths Yann E. MORIN
2014-02-22 12:09 ` Thomas De Schampheleire
2014-02-22 20:45 ` Peter Korsgaard [this message]
2014-02-21 22:17 ` [Buildroot] [PATCH 3/3] manual: add explanations on limitations about using O= Yann E. MORIN
2014-02-22 12:51 ` Thomas De Schampheleire
2014-02-22 13:37 ` Samuel Martin
2014-02-22 20:46 ` Peter Korsgaard
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=87ppmeswp4.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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.