Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] Add the libplayer package
Date: Thu, 06 Oct 2011 10:47:36 +0200	[thread overview]
Message-ID: <87r52q4ic7.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20111006101928.294b6580@skate> (Thomas Petazzoni's message of "Thu, 6 Oct 2011 10:19:28 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 Maxime> +comment "Libplayer requires a toolchain with LARGEFILE support"
 Maxime> +	depends on !BR2_LARGEFILE
 Maxime> +
 >> 
 >> This should go under the 'if BR2_PACKAGE_LIBPLAYER' conditional.

 Thomas> Hu ? We want this comment to be shown when libplayer is *not* enabled,
 Thomas> to let the user know that if (s)he doesn't see libplayer, it's because
 Thomas> largefile is not enabled. So definitely, we don't want this comment to
 Thomas> depend on BR2_PACKAGE_LIBPLAYER. Or am I missing something here ?

No, just me not thinking. Nothing to see here, move along .. ;)

 >> Does libplayer do anything sensible with both backends disabled or do we
 >> need to depend on BR2_PACKAGE_MPLAYER || BR2_PACKAGE_GSTREAMER?

 Thomas> I did ask the same question to Maxime, and libplayer builds fine with
 Thomas> neither backends enabled. It probably doesn't do anything useful, but I
 Thomas> would say that it's the user responsibility here.

Ok.

 >> So it seems you need to depend on BR2_LARGEFILE.

 Thomas> Which it does:

 Maxime> +config BR2_PACKAGE_LIBPLAYER
 Maxime> +	depends on BR2_LARGEFILE

Argh, you're right. I need some more sleep it seems (or atleast stop
trying to do 5 things at once). When testing, I didn't run menuconfig
but just 'make libplayer' and my toolchain didn't have largefile
support.

Sorry about the noise, will commit now - Thanks both.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-10-06  8:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03 10:10 [Buildroot] [pull request v2] Pull request for branch for-2011.11/packages Maxime Ripard
2011-10-03 10:10 ` [Buildroot] [PATCH 1/4] Add the picocom package Maxime Ripard
2011-10-05 19:51   ` Peter Korsgaard
2011-10-03 10:10 ` [Buildroot] [PATCH 2/4] Add Transmission package Maxime Ripard
2011-10-05 20:01   ` Peter Korsgaard
2011-10-07 12:34     ` Maxime Ripard
2011-10-12 15:22   ` [Buildroot] [PATCH] " Maxime Ripard
2011-11-14 12:17     ` Maxime Ripard
2011-11-17 20:03     ` Peter Korsgaard
2011-10-03 10:10 ` [Buildroot] [PATCH 3/4] Add lame support in gstreamer Maxime Ripard
2011-10-05 20:02   ` Peter Korsgaard
2011-10-03 10:10 ` [Buildroot] [PATCH 4/4] Add the libplayer package Maxime Ripard
2011-10-05 20:16   ` Peter Korsgaard
2011-10-06  8:19     ` Thomas Petazzoni
2011-10-06  8:47       ` Peter Korsgaard [this message]
2011-10-06  9:08   ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2011-09-28 11:48 [Buildroot] [pull request] Pull request for branch for-2011.11/packages Maxime Ripard
2011-09-28 11:48 ` [Buildroot] [PATCH 4/4] Add the libplayer package Maxime Ripard
2011-09-30 19:44   ` Thomas Petazzoni
2011-09-30 21:48     ` Maxime Ripard
2011-10-01 11:20       ` 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=87r52q4ic7.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.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