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] package/reactcpp: new package
Date: Wed, 7 Dec 2016 11:24:26 +0100	[thread overview]
Message-ID: <20161207112426.5b40788d@free-electrons.com> (raw)
In-Reply-To: <74b2df33-0865-c6b6-d731-f0e9191223b9@grinn-global.com>

Hello,

On Wed, 7 Dec 2016 10:59:09 +0100, Marcin Niestroj wrote:

> > Just define the version as v$(REACTCPP_VERSION_MAJOR).3  
> 
> I am using $(REACTCPP_VERSION_RAW) below to define $(REACTCPP_SO).

Yes, but REACTCPP_SO is useless, see below.

> >> +ifeq ($(BR2_STATIC_LIBS),)
> >> +define REACTCPP_INSTALL_TARGET_CMDS
> >> +	$(INSTALL) -D -m 0755 $(@D)/src/$(REACTCPP_SO) $(TARGET_DIR)/usr/lib/$(REACTCPP_SO)
> >> +	ln -sf $(REACTCPP_SO) $(TARGET_DIR)/usr/lib/libreactcpp.so.$(REACTCPP_VERSION_MAJOR)
> >> +	ln -sf $(REACTCPP_SO) $(TARGET_DIR)/usr/lib/libreactcpp.so
> >> +endef
> >> +endif  
> >
> > Why are you doing this instead of calling "make install" for
> > $(TARGET_DIR) ?  
> 
> Because make install also copies header files and static library.

And that's perfectly fine. Just let "make install" install header files
and static library. Buildroot will clean them up at the end of the
build, in the "target-finalize" step.

It's much, much better (and future proof) to use the build system of the
package itself when possible, and rely on target-finalize to clean
things up at the end of the build.

Thanks,

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

  reply	other threads:[~2016-12-07 10:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-06 13:26 [Buildroot] [PATCH] package/reactcpp: new package Marcin Niestroj
2016-12-06 15:31 ` Thomas Petazzoni
2016-12-07  9:59   ` Marcin Niestroj
2016-12-07 10:24     ` Thomas Petazzoni [this message]
2016-12-07 11:51       ` Marcin Niestroj
2016-12-07 13:02         ` Thomas Petazzoni
2016-12-07 10:55   ` Marcin Niestroj
2016-12-09  9:21     ` Marcin Niestroj

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=20161207112426.5b40788d@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