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] tinyxml2: fix build in static libs configuration
Date: Thu, 4 May 2017 17:09:41 +0200	[thread overview]
Message-ID: <20170504170941.72731f38@free-electrons.com> (raw)
In-Reply-To: <1493838254-3658-1-git-send-email-rahulbedarkar89@gmail.com>

Hello,

Adding Samuel Martin here, for CMake related discussion below.

On Thu,  4 May 2017 00:34:14 +0530, Rahul Bedarkar wrote:
> tinyxml2 can build both static and shared libraries. By default, only
> shared library is built. Shared/static builds are controlled using
> separate cmake flags BUILD_SHARED_LIBS and BUILD_STATIC_LIBS.
> 
> In static libs configuration, we internally pass -DBUILD_SHARED_LIBS=OFF
> cmake flag to build system which disables both shared and static builds
> of library, resulting in failures while linking executable with library.
> 
> So pass -DBUILD_STATIC_LIBS=ON cmake flag in case of static libs
> configuration.
> 
> fixes:
>   http://autobuild.buildroot.net/results/d30/d301bcbe5db26068b35eaa94bd816ae8cf8ef2e1
> 
> Signed-off-by: Rahul Bedarkar <rahulbedarkar89@gmail.com>
> ---
>  package/tinyxml2/tinyxml2.mk | 4 ++++
>  1 file changed, 4 insertions(+)

Applied to master, thanks.

I think we need to refactor things more globally here though. Why is
pkg-cmake.mk passing BUILD_SHARED_LIBS and not BUILD_STATIC_LIBS ? Why
are some packages passing BUILD_SHARED_LIBS even if it's already passed
by pkg-cmake.mk ?

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

      reply	other threads:[~2017-05-04 15:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 19:04 [Buildroot] [PATCH] tinyxml2: fix build in static libs configuration Rahul Bedarkar
2017-05-04 15:09 ` Thomas Petazzoni [this message]

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=20170504170941.72731f38@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