Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Lindholm <holindho@cs.helsinki.fi>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot: package/gmp toolchain
Date: Sat, 02 Jun 2007 09:01:01 +0300	[thread overview]
Message-ID: <4661079D.90303@cs.helsinki.fi> (raw)
In-Reply-To: <20070601221630.067824855D@busybox.net>

aldot at uclibc.org kirjoitti:
> Author: aldot
> Date: 2007-06-01 15:16:28 -0700 (Fri, 01 Jun 2007)
> New Revision: 18723
> 
> Log:
> - add BR2_PREFER_STATIC_LIB config option to be able to select if we prefer to build static or dynamic libs/bins.
> - depending on the BR2_GNU_BUILD_SUFFIX, set the respective EXEEXT, LIBEXT, SHREXT extensions for use on the target.
> Thanks to Tom for suplying a diff which implements these.
> 
> 
> Modified:
>    trunk/buildroot/Config.in
>    trunk/buildroot/Makefile
>    trunk/buildroot/package/gmp/gmp.mk
>    trunk/buildroot/toolchain/Makefile.in
> 
> 
> Changeset:
> Modified: trunk/buildroot/Config.in
> ===================================================================
> --- trunk/buildroot/Config.in	2007-06-01 19:17:36 UTC (rev 18722)
> +++ trunk/buildroot/Config.in	2007-06-01 22:16:28 UTC (rev 18723)
> @@ -373,6 +373,19 @@
>  	help
>  	  This option hides outdated/obsolete versions of packages.
>  
> +config BR2_PREFER_STATIC_LIB
> +	bool "prefer static libraries"
> +	default n
> +	help
> +	  Where possible, use static libraries.
> +	  This increases your code size a lot and should only be
> +	  used with a good reason why not use the default, which
> +	  is dynamic libraries.
> +
> +	  If unsure, say No.
> +
> +	  WARNING: This is highly experimental at the moment.
> +
>  endmenu
>  
>  source "toolchain/Config.in"
> 
> Modified: trunk/buildroot/Makefile
> ===================================================================
> --- trunk/buildroot/Makefile	2007-06-01 19:17:36 UTC (rev 18722)
> +++ trunk/buildroot/Makefile	2007-06-01 22:16:28 UTC (rev 18723)
> @@ -66,7 +66,32 @@
>  #
>  #############################################################
>  
> +ifneq (,$(findstring linux,$(BR2_GNU_BUILD_SUFFIX)))
> +EXEEXT:=
> +LIBEXT:=.a
> +SHREXT:=.so
> +endif
> +ifneq (,$(findstring apple,$(BR2_GNU_BUILD_SUFFIX)))
> +EXEEXT:=.pear
> +LIBEXT:=.dunno
> +SHREXT:=.dylib
> +endif

Oh, please! How about
EXEEXT:=
LIBEXT:=.a
SHREXT:=.dylib

A while back I submitted a bug report
http://bugs.uclibc.org/view.php?id=1257
which has the places I had to patch hard-coded lib extensions for a 
basic toolchain build. Otherwise, this approach is probably better than 
mine.

-- Heikki Lindholm

  reply	other threads:[~2007-06-02  6:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 22:16 [Buildroot] svn commit: trunk/buildroot: package/gmp toolchain aldot at uclibc.org
2007-06-02  6:01 ` Heikki Lindholm [this message]
2007-06-02  7:16   ` Heikki Lindholm

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=4661079D.90303@cs.helsinki.fi \
    --to=holindho@cs.helsinki.fi \
    --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