Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rahul Jain <rahul.jain@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/6] libubox: enable static build
Date: Wed, 29 Mar 2017 16:08:35 +0530	[thread overview]
Message-ID: <58DB8EAB.2030309@imgtec.com> (raw)
In-Reply-To: <29802569-43e0-ee44-da29-d7f76d6002d9@mind.be>

Hi Arnout,

Thanks for your comments.

On Friday 24 March 2017 06:37 PM, Arnout Vandecappelle wrote:
>
>
> On 24-03-17 13:49, Rahul Jain wrote:
>> upstream has added the support to build the static libraries.
>> update comment for BR2_STATIC_LIBS for other packages having
>> dependency on libubox.
>
>   The reason why that comment is there, is so we remember that when libubox is
> allowed to be built statically, we should check if ubus and ustream-ssl perhaps
> now also can be built statically. So, did you check that? If yes, you should
> update the comment as to why they can't be build statically (e.g. "dlopen()",
> see other Config.in files).

I have checked package cmake files and found out that there is no 
support for building static libraries in ubus and ustream-ssl packages.
I will add a comment '#no support to build static libraries in config file'.

  reply	other threads:[~2017-03-29 10:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24 12:49 [Buildroot] [PATCH 1/6] libubox: bump version Rahul Jain
2017-03-24 12:49 ` [Buildroot] [PATCH 2/6] ubus: " Rahul Jain
2017-03-24 12:49 ` [Buildroot] [PATCH 3/6] libuci: " Rahul Jain
2017-03-24 12:49 ` [Buildroot] [PATCH 4/6] uhttpd: " Rahul Jain
2017-03-24 12:49 ` [Buildroot] [PATCH 5/6] ustream-ssl: " Rahul Jain
2017-03-24 12:49 ` [Buildroot] [PATCH 6/6] libubox: enable static build Rahul Jain
2017-03-24 13:07   ` Arnout Vandecappelle
2017-03-29 10:38     ` Rahul Jain [this message]
2017-03-29 12:38       ` Arnout Vandecappelle
2017-03-25 14:15 ` [Buildroot] [PATCH 1/6] libubox: bump version 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=58DB8EAB.2030309@imgtec.com \
    --to=rahul.jain@imgtec.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