From: Simon Rowe <Simon.Rowe@citrix.com>
To: buildroot@busybox.net
Subject: [Buildroot] External packages in 2020.02
Date: Thu, 26 Mar 2020 12:56:01 +0000 [thread overview]
Message-ID: <1585227360690.38607@citrix.com> (raw)
Has something changed in the way that packages external to the buildroot code tree need to be specified? After updating my 2019.02 config I can no longer see my external package in the config menu.
I've checked Config.in, external.desc and external.mk but they seem to contain the correct details,
Simon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200326/d962d951/attachment.html>
reply other threads:[~2020-03-26 12:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1585227360690.38607@citrix.com \
--to=simon.rowe@citrix.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.