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 14:02:00 +0100	[thread overview]
Message-ID: <20161207140200.3873c08e@free-electrons.com> (raw)
In-Reply-To: <29623960-22c5-ee30-a5fd-69692019e56c@grinn-global.com>

Hello,

On Wed, 7 Dec 2016 12:51:24 +0100, Marcin Niestroj wrote:

> > 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.  
> 
> Ok, I was not aware cleaning header and *.a files in target-finalize.
> 
> I have used 'make install' and checked the target directory before and
> after target-finalize. There was *.a symlink pointing to *.a.1.0.3.
> After target-finalize only the symlink was removed. How should we fix
> that?

Then you can do a POST_INSTALL_TARGET_HOOKS to remove this additional
file.

It is very weird to create a static library file name with a version
number. Normally, static libraries are directly installed as
lib<foo>.a.

Thanks!

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

  reply	other threads:[~2016-12-07 13:02 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
2016-12-07 11:51       ` Marcin Niestroj
2016-12-07 13:02         ` Thomas Petazzoni [this message]
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=20161207140200.3873c08e@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