Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] bctoolbox: new package
Date: Tue, 07 Feb 2017 12:20:51 +0100	[thread overview]
Message-ID: <87mvdytffw.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170122210021.9463-1-joerg.krause@embedded.rocks> ("Jörg Krause"'s message of "Sun, 22 Jan 2017 22:00:20 +0100")

>>>>> "J?rg" == J?rg Krause <joerg.krause@embedded.rocks> writes:

 > bctoolbox is a utilities library used by Belledonne Communications
 > softwares like belle-sip, mediastreamer2 and linphone.

 > Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>

This seems to break building ortp statically:

http://autobuild.buildroot.org/?reason=ortp-0.27.0

Looking further, it comes from the bctoolbox pkg-config file
libs.private:

bctoolbox-0.4.0/bctoolbox.pc.in:
Libs.private: @LIBS_PRIVATE@

Which gets populated from cmake:

bctoolbox-0.4.0/CMakeLists.txt:

if(MBEDTLS_FOUND)
        get_filename_component(mbedtls_library_path "${MBEDTLS_LIBRARIES}" PATH)
        set(LIBS_PRIVATE "${LIBS_PRIVATE} -L${mbedlts_library_path}")
endif()

mbedtls_library_path is apparently the empty string, so it ends up just
with "-L".

Samuel/J?rg, any idea how this should work?

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2017-02-07 11:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22 21:00 [Buildroot] [PATCH v2 1/2] bctoolbox: new package Jörg Krause
2017-01-22 21:00 ` [Buildroot] [PATCH v2 2/2] package/ortp: bump version to 0.27.0 Jörg Krause
2017-01-24  9:39   ` Thomas Petazzoni
2017-01-24  9:36 ` [Buildroot] [PATCH v2 1/2] bctoolbox: new package Thomas Petazzoni
2017-02-07 11:20 ` Peter Korsgaard [this message]
2017-02-07 12:54   ` Jörg Krause
2017-02-07 13:24     ` Peter Korsgaard

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=87mvdytffw.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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