From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] modplugtools: Added package
Date: Sun, 19 Oct 2014 11:11:54 +0200 [thread overview]
Message-ID: <20141019091154.GI4072@free.fr> (raw)
In-Reply-To: <108749465.hOBsSJgTxk@hyperion>
Maarten, All,
On 2014-10-19 01:28 +0200, Maarten ter Huurne spake thusly:
> On Saturday 18 October 2014 23:57:48 Yann E. MORIN wrote:
> > On 2014-10-18 22:04 +0200, Maarten ter Huurne spake thusly:
> > > diff --git a/package/modplugtools/Config.in
> > > b/package/modplugtools/Config.in new file mode 100644
> > > index 0000000..20009b6
> > > --- /dev/null
> > > +++ b/package/modplugtools/Config.in
> > > @@ -0,0 +1,9 @@
> > > +config BR2_PACKAGE_MODPLUGTOOLS
> > > + bool "modplugtools"
> > > + select BR2_PACKAGE_LIBAO
> > > + select BR2_PACKAGE_LIBMODPLUG
> >
> > modplugtools should inherit the dependencies from libmodplug, namely
> > C++:
> >
> > config BR2_PACKAGE_MODPLUGTOOLS
> > bool "modplugtools"
> > depends on BR2_INSTALL_LIBSTDCPP # libmodplug
> > select BR2_PACKAGE_LIBMODPLUG
> > select BR2_PACKAGE_LIBAO
>
> Hmm, I didn't expect to have to propagate dependencies manually.
Yes, see chapter 16.2.1, 'Choosing depends on or select' in the manual:
http://buildroot.net/downloads/manual/manual.html#_literal_config_in_literal_file
Quoting:
Note. The current problem with the kconfig language is that these
two dependency semantics are not internally linked. Therefore, it may be
possible to select a package, whom one of its dependencies/requirement
is not met.
> On the
> other hand, if Kconfig tried to do this automatically, including supporting
> conditional dependencies, it might end up as a full Prolog interpreter. ;)
He! :-)
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-10-19 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 3:19 [Buildroot] [PATCH] sdl_mixer: Enable support for libmodplug Maarten ter Huurne
2014-10-18 13:42 ` Arnout Vandecappelle
2014-10-18 20:04 ` [Buildroot] [PATCH v2] modplugtools: Added package Maarten ter Huurne
2014-10-18 21:57 ` Yann E. MORIN
2014-10-18 23:28 ` Maarten ter Huurne
2014-10-19 9:11 ` Yann E. MORIN [this message]
2014-10-19 0:00 ` [Buildroot] [PATCH v3] " Maarten ter Huurne
2014-10-19 9:25 ` Yann E. MORIN
2014-10-19 9:41 ` Thomas Petazzoni
2014-10-19 10:22 ` [Buildroot] [PATCH] sdl_mixer: Enable support for libmodplug 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=20141019091154.GI4072@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