Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Scheel <julian@jusst.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] dvblast: new package
Date: Sun, 18 Oct 2015 22:13:38 +0200	[thread overview]
Message-ID: <5623FD72.9010306@jusst.de> (raw)
In-Reply-To: <20151018160612.1bb09b23@free-electrons.com>

Hi Thomas,

On 18.10.15 16:06, Thomas Petazzoni wrote:
>> Address review comments by Yann E. Morin (thanks for review!)
>> - Complete license information
>> - Remove explicit INSTALL_STAGING=no
>
> You should have also removed INSTALL_TARGET = YES, because that's the
> default.

Ack, makes sense.

>> - Fix install command
>>
>> The build cmd is not changed to use TARGET_CONFIGURE_OPTS as it breaks the
>> build.
>
> A working solution is to pass TARGET_CONFIGURE_OPTS in the environment
> of make instead of as an option. This ensures that the CFLAGS += in the
> dvblast Makefile are still taken into account.

Ah, thanks, good to know. I'll keep it in mind.

> So, I've applied you patch, with the following changes:
>
>      [Thomas:
>       - add missing hash file.

Nice, I actually hadn't even realized that buildroot has hash files so 
far :)

>       - rewrap Config.in help text
>       - remove unneeded "DVBLAST_INSTALL_TARGET = YES", since this is the
>         default behavior
>       - pass TARGET_MAKE_ENV in the environment when calling make.
>       - use TARGET_CONFIGURE_OPTS instead of just CC/LD.]
>
> Thanks a lot!

Thanks for applying.

-Julian

  reply	other threads:[~2015-10-18 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-18 12:34 [Buildroot] [PATCH v2 1/2] bitstream: new package Julian Scheel
2015-10-18 12:34 ` [Buildroot] [PATCH v2 2/2] dvblast: " Julian Scheel
2015-10-18 14:06   ` Thomas Petazzoni
2015-10-18 20:13     ` Julian Scheel [this message]
2015-10-18 13:54 ` [Buildroot] [PATCH v2 1/2] bitstream: " 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=5623FD72.9010306@jusst.de \
    --to=julian@jusst.de \
    --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