Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Introduction of mpd into buildroot ?
Date: Thu, 23 Sep 2010 00:09:22 +0100	[thread overview]
Message-ID: <20100923000922.57de215a@surf> (raw)
In-Reply-To: <AANLkTimZa473TfBgFhoXMhR_fiusyduFvdo-YuMzs84T@mail.gmail.com>

Hello Yoann,


On Wed, 22 Sep 2010 14:45:49 +0200
Yoann Sculo <yoann.sculo@gmail.com> wrote:

> First, I'd like to have your opinion about pkg-config files. libmad-0.15.1
> for example doesn't provide the small file mad.pc
> This is surprising, It does'nt seem to be distributed with libmad sources.
> The probem is I need actually this file to compile mpd. Adding it manually,
> works fine.
> 
> So I would be inclined to create a patch into package/multimedia/libmad to
> add this file during mpd installation. Is it the better way to do this ?

Yes, sounds good. An even better thing would be to create such a patch
*and* to submit it to the upstream libmad project so that hopefully a
future version of libmad will contain the pkg-config file.

> Well, if mpd has never been added into buildroot I'm interested to work on
> it.

I haven't heard of any effort to package mpd, so feel free to work on
it!

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2010-09-22 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 12:45 [Buildroot] Introduction of mpd into buildroot ? Yoann Sculo
2010-09-22 13:05 ` Lionel Landwerlin
2010-09-22 23:09 ` Thomas Petazzoni [this message]
2010-09-23 15:53   ` Yoann Sculo
2010-09-23 21:19   ` 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=20100923000922.57de215a@surf \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox