From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] infozip: new package
Date: Thu, 10 Jan 2013 12:15:11 +0100 [thread overview]
Message-ID: <20130110121511.0d25e449@skate> (raw)
In-Reply-To: <1357814466-3728-1-git-send-email-jp@jp-embedded.com>
Dear Jan Pedersen,
On Thu, 10 Jan 2013 11:41:06 +0100, Jan Pedersen wrote:
> +INFOZIP_LICENSE_FILES = LICENCE
This is not correct, the file is called LICENSE.
You should run "make legal-info" when you create a new package, to
verify that the LICENSE_FILES field is correct.
> +define INFOZIP_BUILD_CMDS
> + $(MAKE) -C $(@D) -f unix/Makefile generic CC=$(TARGET_CC)
> +endef
> +
> +define INFOZIP_INSTALL_TARGET_CMDS
> + $(MAKE) -C $(@D) -f unix/Makefile install prefix=$(TARGET_DIR)/usr CC=$(TARGET_CC)
> +endef
Even though the package does not allow to override CFLAGS, I would
prefer if $(TARGET_CONFIGURE_OPTS) was used. It avoids for example the
mistake of forgetting the quotes around $(TARGET_CC). So, something
like:
define INFOZIP_BUILD_CMDS
$(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) -f unix/Makefile generic
endef
define INFOZIP_INSTALL_TARGET_CMDS
$(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) -f unix/Makefile install prefix=$(TARGET_DIR)/usr
endef
Once this is fixed, you get my Acked-by and Tested-by, as I tested this
package.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-10 11:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 10:41 [Buildroot] [PATCH 1/1] infozip: new package Jan Pedersen
2013-01-10 11:15 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-11 9:45 Jan Pedersen
2013-01-11 20:25 ` Arnout Vandecappelle
2013-01-14 13:30 Jan Pedersen
2013-01-14 13:32 ` Thomas Petazzoni
2013-01-14 15:54 ` 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=20130110121511.0d25e449@skate \
--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