All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] Add the libplayer package
Date: Fri, 30 Sep 2011 23:48:22 +0200	[thread overview]
Message-ID: <4E863926.50903@free-electrons.com> (raw)
In-Reply-To: <20110930214449.5139eb84@skate>

Hi,

Le 30/09/2011 21:44, Thomas Petazzoni a ?crit :
> Le Wed, 28 Sep 2011 13:48:34 +0200,
> Maxime Ripard<maxime.ripard@free-electrons.com>  a ?crit :
>> +config BR2_PACKAGE_LIBPLAYER_MPLAYER
>> +	depends on BR2_PACKAGE_MPLAYER
>> +	bool "Libplayer mplayer backend"
>> +
>> +config BR2_PACKAGE_LIBPLAYER_GSTREAMER
>> +	depends on BR2_PACKAGE_GSTREAMER
>> +	bool "Libplayer GStreamer backend"
>
> What happens if we select none of those backends ?

Hmmm, good question. I'll check.

>> +define LIBPLAYER_CONFIGURE_CMDS
>> +	(cd $(@D)&&  rm -rf config.cache&&  \
>> +	$(TARGET_CONFIGURE_OPTS) \
>> +	$(TARGET_CONFIGURE_ARGS) \
>> +	$(LIBPLAYER_CONF_ENV) \
>
> LIBPLAYER_CONF_ENV is not defined anywhere.

Ah, you're right, I missed that one.

>
>> +	./configure \
>> +		--prefix=/usr \
>> +		--cross-compile \
>> +		$(SHARED_STATIC_LIBS_OPTS) \
>> +		$(QUIET) $(LIBPLAYER_CONF_OPT) \
>> +	)
>
> This looks like a normal ./configure invocation. Why don't you use the
> default foo_CONFIGURE_CMDS provided by the autotargets infrastructure ?

The configure script breaks if we pass --target or --host, I did this to 
avoid it.

>> +ifeq ($(BR2_PACKAGE_LIBPLAYER_PYTHON),y)
>
> This option is not defined in your Config.in.

Ah, yup.

I'll resend the whole patchset once it will be updated.

Maxime

  reply	other threads:[~2011-09-30 21:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 1/4] Add the picocom package Maxime Ripard
2011-09-30 19:46   ` Thomas Petazzoni
2011-09-28 11:48 ` [Buildroot] [PATCH 2/4] Add Transmission package Maxime Ripard
2011-09-28 12:11   ` Thomas Petazzoni
2011-09-28 11:48 ` [Buildroot] [PATCH 3/4] Add lame support in gstreamer 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 [this message]
2011-10-01 11:20       ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
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 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
2011-10-06  9:08   ` 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=4E863926.50903@free-electrons.com \
    --to=maxime.ripard@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 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.