CODEWITHSUNDEEP
cmakebitbake
Chris Morgan
Chris Morgan

Reputation: 1339

Bitbake vs. cmake for x86 and arm project

I have a layered cmake project with a hierarchy of libraries and applications. Each of these libraries and applications has a CMakeLists.txt and a top level CMakeLists.txt that includes the sub-cmake files.

Right now we are developing and testing entirely on an x86 Linux platform but at some point we will want to start pulling the code into a Yocto build and target arm. We want to maintain being able to build for both x86 and arm.

I've seen some Yocto guides on building for x86 but these appear to build the entire world (the toolchain, linux kernel, all libraries etc) and run the image via qemu. For our desktop use this is quite a bit of overkill when our machines have compilers and we can just run the applications directly, but it would be very helpful to have bitbake build some libraries that we have dependencies on and that need to be installed to a 'virtual root'.

How can I use use bitbake for native x86 projects (in place of or in addition to cmake) and be able to leverage the recipe files for Yocto later on?

Upvotes: 2

Views: 2808

Answers (1)

yegorich
yegorich

Reputation: 4849

I don't have much experience with Yocto, but I'm using another embedded Linux distribution with similar concept: Buildroot. Buildroot creates toolchainfile (output/host/usr/share/buildroot/toolchainfile.cmake) for the currently selected toolchain.

You create two output folders for your project:

build-x86
build-arm

I the first folder you just execute:

cmake ../path-to-your-source

In the second one:

cmake ../path-to-your-source -DCMAKE_TOOLCHAIN_FILE=../path-to-buildroot/output/host/usr/share/buildroot/toolchainfile.cmake

If Yocto provides a toolchainfile, you can use it directly. If not you can create it yourself. See this wiki.

Update:

This section explains, how you can add your software to Buildroot (package). Here the source folder override mechanism is described.

Upvotes: 1

Related Questions