From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnout Vandecappelle Date: Wed, 18 Sep 2013 23:57:41 +0200 Subject: [Buildroot] [PATCH 3 of 4 RFC] manual: add section about depending on toolchain options In-Reply-To: <20130918201812.3e08d883@skate> References: <89b40887c8268e316399.1379494896@argentina> <20130918183414.45e6a247@skate> <20130918194042.302e9afe@skate> <5239E6E5.4000401@zacarias.com.ar> <20130918195925.1884c0a7@skate> <5239EB63.2090203@zacarias.com.ar> <20130918201812.3e08d883@skate> Message-ID: <523A21D5.6040005@mind.be> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On 18/09/13 20:18, Thomas Petazzoni wrote: > Dear Gustavo Zacarias, > > On Wed, 18 Sep 2013 15:05:23 -0300, Gustavo Zacarias wrote: >> On 09/18/2013 02:59 PM, Thomas Petazzoni wrote: >> >>> I think it's a bit more than just renaming this symbol. I can try to >>> cook something. >> >> Add the relevant legacy entry, adjusting help / manuals. >> Is there something else i'm missing? > > Yes, we probably want to have the choice between building static only, > static + shared, or shared only, default to shared only. Currently, > when !BR2_PREFER_STATIC_LIB, we build both the shared and static > variants, which takes time because it requires building everything > twice, once with -fPIC, once without. I don't think the static + shared option really makes sense, does it? The only use case I can think of is when you want a proprietary executable to link statically in order to speed up start time. Regards, Arnout -- Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F