From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Wed, 3 May 2017 11:35:09 +0200 Subject: [Buildroot] Cross-compiling out-of-tree kernel modules and user-space apps In-Reply-To: <4e87c694-21a2-7f06-9d88-f736e832e061@free.fr> References: <4e87c694-21a2-7f06-9d88-f736e832e061@free.fr> Message-ID: <20170503113509.0d5cd238@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Wed, 3 May 2017 11:15:15 +0200, Mason wrote: > I use buildroot to generate kernel + rootfs image for an ARM > platform, typically cross-compiled with the Linaro toolchain. > > I also have a large body of software in a separate repo > (outside of the BR tree) with its own build system. What do you call "its own build system" ? > This repo includes kernel modules, user-space libraries > and apps, which need to be cross-compiled and built on > top of the rootfs generated by BR. > > Therefore, I would need to pass some information from BR > to the separate build system, such as > > - ARCH > - CROSS_COMPILE > - location of the cross-toolchain, to add to the PATH > - location of the sysroot > > What is the best way to do this? Create Buildroot packages for the different software components you need to build. Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com