From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnout Vandecappelle Date: Sun, 25 Nov 2012 23:25:37 +0100 Subject: [Buildroot] Passing arguments to the linker when external toolchain is used. In-Reply-To: References: <50B15945.90300@mind.be> <50B28348.7090701@mind.be> Message-ID: <50B29AE1.1000100@mind.be> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On 25/11/12 21:56, Ronny Meeus wrote: > On Sun, Nov 25, 2012 at 9:44 PM, Arnout Vandecappelle wrote: [snip] >> In that case, why not just pass them with LDFLAGS? >> > > Our SW is build in 2 parts: the Linux kernel, buildroot and other > components are build via buildroot itself. > Next to this we also have other applications that we build in with "a > private build infrastructure" using the toolchain, include files etc > of buildroot. > > By adding the extra linker parameters with the wrapper construction we > can transparantly introduce a new toolchain (with the required > parameters) in that environment without impact on our build > infrastructure. The big advantage is that the complete toolchain > selection (CPU,ABI etc) only needs to be done in buildroot. Yes, sounds like a valid use case. I also expect that the LDFLAGS are not passed reliably for all packages: they are hardly ever used, and there are no autobuilder configurations with any LDFLAGS, so errors in passing LDFLAGS can go unnoticed. I don't think we have any other architecture currently in buildroot that requires something to be passed to ld. If this wrapper construction is added to buildroot, it would be good if we would also have an internal use case. Regards, Arnout -- Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286540 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