From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] bctoolbox: disable rpath
Date: Sun, 19 Feb 2017 16:07:35 +0100 [thread overview]
Message-ID: <1487516855.17793.1.camel@embedded.rocks> (raw)
In-Reply-To: <20170215095650.236f21b5@free-electrons.com>
Hi,
On Wed, 2017-02-15 at 09:56 +0100, Thomas Petazzoni wrote:
> Hello,
>
> On Wed, 15 Feb 2017 07:28:46 +0200, Baruch Siach wrote:
> > Hi J?rg,
> >
> > On Tue, Feb 14, 2017 at 11:44:02PM +0100, J?rg Krause wrote:
> > > By default, bctoolbox adds the rpath to the shared library.
> > > Prevent this
> > > by setting `CMAKE_SKIP_RPATH` [1] to a true value.
> > >
> > > [1] https://cmake.org/cmake/help/latest/variable/CMAKE_SKIP_RPATH
> > > .html
> > >
> > > Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> > > ---
> > > ?package/bctoolbox/bctoolbox.mk | 5 ++++-
> > > ?1 file changed, 4 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/package/bctoolbox/bctoolbox.mk
> > > b/package/bctoolbox/bctoolbox.mk
> > > index 5eea0575f..76737aa3c 100644
> > > --- a/package/bctoolbox/bctoolbox.mk
> > > +++ b/package/bctoolbox/bctoolbox.mk
> > > @@ -11,11 +11,14 @@ BCTOOLBOX_LICENSE_FILES = COPYING
> > > ?BCTOOLBOX_DEPENDENCIES = mbedtls
> > > ?BCTOOLBOX_INSTALL_STAGING = YES
> > > ?
> > > +# Set CMAKE_SKIP_RPATH to prevent bctoolbox from adding the
> > > rpath to
> > > +# shared library.
> > > ?BCTOOLBOX_CONF_OPTS = \
> > > ? -DENABLE_STRICT=OFF \
> > > ? -DENABLE_TESTS_COMPONENT=OFF \
> > > ? -DENABLE_TESTS=OFF \
> > > - -DGIT_EXECUTABLE=OFF
> > > + -DGIT_EXECUTABLE=OFF \
> > > + -DCMAKE_SKIP_RPATH=ON??
> >
> > Shouldn't we have this in package/pkg-cmake.mk? Samuel?
>
> Indeed, it's a generic CMake option, so it should be in
> package/pkg-cmake.mk IMO.
opencv and opencv3 both set this option on a package level.
> Worth mentioning that there is both CMAKE_SKIP_RPATH and
> CMAKE_SKIP_INSTALL_RPATH. The former skips adding the rpath during
> both
> the build and install steps, which prevents from running the binary
> from the build directory. The latter only skips the rpath during the
> install step. But since we're cross-compiling, running on the host
> machine from the build directory anyway doesn't make sense. So
> CMAKE_SKIP_RPATH is OK.
>
> See https://cmake.org/cmake/help/v3.0/variable/CMAKE_SKIP_RPATH.html.
Samuel argues not to force this option by the infrastructure. I am
not sure how do we handle this properly. So, what shall we do?
Best regards,
J?rg Krause
next prev parent reply other threads:[~2017-02-19 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 22:43 [Buildroot] [PATCH 1/4] Revert "bctoolbox: fix typos and logic error" Jörg Krause
2017-02-14 22:44 ` [Buildroot] [PATCH 2/4] bctoolbox: add patch to fix static linking Jörg Krause
2017-02-14 22:44 ` [Buildroot] [PATCH 3/4] bctoolbox: fix mbedtls/polarssl dependency Jörg Krause
2017-02-14 22:44 ` [Buildroot] [PATCH 4/4] bctoolbox: disable rpath Jörg Krause
2017-02-15 5:28 ` Baruch Siach
2017-02-15 6:12 ` Samuel Martin
2017-02-15 8:58 ` Thomas Petazzoni
2017-02-15 8:56 ` Thomas Petazzoni
2017-02-19 15:07 ` Jörg Krause [this message]
2017-02-19 17:44 ` Thomas Petazzoni
2017-02-20 21:25 ` [Buildroot] [PATCH 1/4] Revert "bctoolbox: fix typos and logic error" 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=1487516855.17793.1.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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