Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V2 1/2] tcl: add support for static builds
Date: Sat, 7 Mar 2015 15:28:50 +0100	[thread overview]
Message-ID: <54FB0B22.8050604@imgtec.com> (raw)
In-Reply-To: <20150307144233.5ee1db01@free-electrons.com>

Dear Thomas Petazzoni,

On 07/03/15 14:42, Thomas Petazzoni wrote:
> Dear Vicente Olivert Riera,
> 
> On Sat, 7 Mar 2015 13:22:41 +0000, Vicente Olivert Riera wrote:
> 
>> +ifeq ($(BR2_STATIC_LIBS),y)
>> +# Do not build tclsh with dynamic loading support when building it
>> +# statically because it needs dlopen() and friends.
>> +TCL_CONF_OPTS += --disable-load
>> +# Also, build only the binaries and libraries and don't build the
>> +# 'packages' because they are shared objects which are intended to be
>> +# loaded dynamically.
>> +TCL_MAKE_OPTS = binaries libraries
>> +TCL_INSTALL_STAGING_OPTS = DESTDIR=$(STAGING_DIR) install-binaries install-libraries
>> +TCL_INSTALL_TARGET_OPTS = DESTDIR=$(TARGET_DIR) install-binaries
>> +endif
> 
> But, if we don't build the 'packages', is the tcl stuff still useful?

I guess you could need tcl to build something that depends on it, and
link against libtcl8.6.a, for instance.

Regards,
--
Vincent

> Best regards,
> 
> Thomas
> 

  reply	other threads:[~2015-03-07 14:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07 13:22 [Buildroot] [PATCH V2 1/2] tcl: add support for static builds Vicente Olivert Riera
2015-03-07 13:22 ` [Buildroot] [PATCH V2 2/2] tcl: rename BR2_PACKAGE_TCL_SHLIB_ONLY to be more consistent Vicente Olivert Riera
2015-03-07 13:43   ` Thomas Petazzoni
2015-03-07 13:42 ` [Buildroot] [PATCH V2 1/2] tcl: add support for static builds Thomas Petazzoni
2015-03-07 14:28   ` Vicente Olivert Riera [this message]
2015-03-07 14:56     ` Thomas Petazzoni
2015-03-07 15:05       ` Vicente Olivert Riera
2015-03-07 15:35         ` Thomas Petazzoni
2015-03-07 16:12           ` Vicente Olivert Riera
2015-03-07 16:44   ` Arnout Vandecappelle

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=54FB0B22.8050604@imgtec.com \
    --to=vincent.riera@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