From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] yajl: fix static linking in a parallel build
Date: Sat, 2 Apr 2016 17:13:18 +0200 [thread overview]
Message-ID: <20160402171318.653fec21@free-electrons.com> (raw)
In-Reply-To: <1459538292-7023-1-git-send-email-joerg.krause@embedded.rocks>
Hello,
On Fri, 1 Apr 2016 21:18:12 +0200, J?rg Krause wrote:
> + FOREACH (test ${TESTS})
> + GET_FILENAME_COMPONENT(testProg ${test} NAME_WE)
> + ADD_EXECUTABLE(${testProg} ${test})
> +- TARGET_LINK_LIBRARIES(${testProg} yajl m)
> ++ TARGET_LINK_LIBRARIES(${testProg} yajl_s m)
I am not sure to understand why this would fix the parallel build
issue. The parallel build problem comes from the fact that the library
and tests sit in different directories, and that they are built in
parallel with each other. Both the yajl and yajl_s libraries are built
in the same directory, separate from the tests directory. So I don't
quite see how changing from using yajl to yajl_s is going to make a
difference here. But maybe I'm missing something.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-02 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 19:18 [Buildroot] [PATCH] yajl: fix static linking in a parallel build Jörg Krause
2016-04-02 15:13 ` Thomas Petazzoni [this message]
2016-04-02 16:29 ` Jörg Krause
2016-04-02 17:05 ` Samuel Martin
2016-04-02 17:11 ` Jörg Krause
2016-04-02 17:43 ` Samuel Martin
2016-04-02 18:18 ` Jörg Krause
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=20160402171318.653fec21@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