From: Maarten ter Huurne <maarten@treewalker.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] modplugtools: Added package
Date: Sat, 18 Oct 2014 19:19:46 +0200 [thread overview]
Message-ID: <5202496.NH7UHFfB86@hyperion> (raw)
In-Reply-To: <54427584.5060903@mind.be>
On Saturday 18 October 2014 16:13:24 Arnout Vandecappelle wrote:
> On 17/10/14 19:10, Maarten ter Huurne wrote:
> > diff --git a/package/modplugtools/Config.in
> > b/package/modplugtools/Config.in new file mode 100644
> > index 0000000..53e9672
> > --- /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
> > + help
> > + This installs the 'modplug123' command line tool to play music
files
> > + using libmodplug.
>
> Small nit: I'd say "MOD files" rather than "music files". Or does it play
> other formats as well?
It plays various tracker formats. I tested it with S3M files, for example. I
considered "tracker songs" instead of "music files", but I wasn't sure
whether "tracker" is still a commonly understood term.
> > +
> > +MODPLUGTOOLS_DEPENDENCIES = libao libmodplug
> > +
> > +# Only play through libao: some platforms don't have OSS support and
> > for those +# that do, playing through libao is still going to be
> > sufficient. +define MODPLUGTOOLS_REMOVE_MODPLUGPLAY
> > + rm $(TARGET_DIR)/usr/bin/modplugplay
>
> I don't understand this. The executable is really small, and it builds
> correctly (otherwise you wouldn't even get this far), so why bother with
> removing it? Someone who cares that much about their rootfs size will have
> to remove a bunch of other stuff from the installed system anyway.
It wouldn't execute correctly on target systems that don't have OSS support.
Since OSS has been deprecated in the kernel for many years (*), my hope is
that most embedded kernels today don't have OSS support.
(*) I tried to look up how long, but it predates the move to Git in 2005.
Bye,
Maarten
next prev parent reply other threads:[~2014-10-18 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 17:10 [Buildroot] [PATCH] modplugtools: Added package Maarten ter Huurne
2014-10-18 14:13 ` Arnout Vandecappelle
2014-10-18 17:19 ` Maarten ter Huurne [this message]
2014-10-18 17:44 ` Yann E. MORIN
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=5202496.NH7UHFfB86@hyperion \
--to=maarten@treewalker.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox