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] [PATCH] fmt: new package
Date: Thu, 6 Apr 2017 12:53:12 +0200	[thread overview]
Message-ID: <20170406125312.3675b60a@free-electrons.com> (raw)
In-Reply-To: <1491474619-11636-1-git-send-email-semenak94@mail.ru>

Hello,

Thanks for this new version. For new versions, it is better if the
subject prefix is change, and you include a changelog.

To change the subject prefix:

	git format-patch -v2 HEAD^

will change [PATCH] into [PATCHv2]

On Thu,  6 Apr 2017 13:30:19 +0300, Semyon Kolganov wrote:
> Signed-off-by: Semyon Kolganov <semenak94@mail.ru>
> ---

And the changelog can be written here, detailing what changed between
v1 and v2.

> diff --git a/package/fmt/Config.in b/package/fmt/Config.in
> new file mode 100644
> index 0000000..9ce2874
> --- /dev/null
> +++ b/package/fmt/Config.in
> @@ -0,0 +1,6 @@
> +config BR2_PACKAGE_FMT
> +	bool "fmt"

Missed this on the first review: since this is a C++ package, you need
to do:

	depends on BR2_INSTALL_LIBSTDCPP

> +	help
> +	  fmt is an open-source formatting library for C++. It can be used
> +	  as a safe alternative to printf or as a fast alternative to
> +	  IOStreams.
> \ No newline at end of file

Still a missing new line here.

And since there's now a C++ dependency, you must add:

comment "fmt needs a toolchain w/ C++"
	depends on !BR2_INSTALL_LIBSTDCPP

> +FMT_CONF_OPTS = \
> +	-DHAVE_OPEN=ON \
> +	-DFMT_INSTALL=ON \
> +	-DFMT_TEST=OFF
> +
> +define FMT_INSTALL_STAGING_CMDS
> +	mkdir -p $(STAGING_DIR)/usr/include/fmt
> +	cp -dpfr $(@D)/fmt/*.h $(STAGING_DIR)/usr/include/fmt
> +endef

I still don't get this. For the target installation, you're using the
"make install" from the CMake packaging, but for the staging
installation, you're overriding the logic to only install the header
files. Why?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-04-06 10:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fmt: new package>
2017-04-06 10:30 ` [Buildroot] [PATCH] fmt: new package Semyon Kolganov
2017-04-06 10:53   ` Thomas Petazzoni [this message]
2017-04-06 12:02 ` [Buildroot] [PATCHv2] fmt: new package PATCHv2 Semyon Kolganov
2017-04-06 14:00   ` Thomas Petazzoni
2017-04-06 14:17 ` [Buildroot] [PATCHv3] fmt: new package PACKAGEv3 Semyon Kolganov
2017-04-06 14:27 ` [Buildroot] [PATCHv4] fmt: new package Semyon Kolganov
2017-04-06 15:29   ` Baruch Siach
2017-04-06 15:41 ` [Buildroot] [PATCHv5] " Semyon Kolganov
2017-04-06 20:14   ` 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=20170406125312.3675b60a@free-electrons.com \
    --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