From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11481] New: Docs: Is external.desc required?
Date: Fri, 02 Nov 2018 11:26:30 +0000 [thread overview]
Message-ID: <bug-11481-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11481
Bug ID: 11481
Summary: Docs: Is external.desc required?
Product: buildroot
Version: 2018.08.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: imphil at philipp-wagner.com
CC: buildroot at uclibc.org
Target Milestone: ---
I have a minor docs comment.
https://buildroot.org/downloads/manual/manual.html#customize
In the user guide, section "9.1. Recommended directory structure" the directory
tree shows two files for a br2 external tree:
=====
+-- Config.in (if using a br2-external tree)
+-- external.mk (if using a br2-external tree)
=====
The documentation further down suggests that three files are needed:
=====
9.2.1. Layout of a br2-external tree
A br2-external tree must contain at least those three files, described in the
following chapters:
external.desc
external.mk
Config.in
=====
Most likely the external.desc file is missing from the top section?
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-11-02 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 11:26 bugzilla at busybox.net [this message]
2018-11-02 11:51 ` [Buildroot] [Bug 11481] Docs: Is external.desc required? bugzilla at busybox.net
2018-11-02 20:31 ` bugzilla at busybox.net
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=bug-11481-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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