[yocto] Trying to Integrate QNX's Neutrino 6.5.0 toolcain into OE/Yocto as a foreign (external) tool-chain

Glenn Schmottlach gschmottlach at gmail.com
Wed Jun 19 14:05:00 PDT 2013


The company I work for tends to do a fair amount of work in both Linux and
QNX. Primarily we use the Bitbake/OpenEmbedded/Yocto build framework to
build individual recipes (packages, e.g. libraries, apps, etc...) and
ultimately Linux BSP images for several HW platforms and CPUs. As I
understand it the OpenEmbedded framework supports external (binary)
tool-chains (e.g. like those provided with QNX's Linux host tools which are
gcc based) so my thoughts have been focused on integrating the QNX
tool-chain into the OpenEmbedded/Yocto framework. Ideally, with suitable
recipes and the layering system provided by the framework, it seems
plausible that I *should* be able to generate QNX
executables/libraries/images using this build framework on a Linux host.

Has anyone out there attempted this? Is this even feasible since OE/Yocto
tends to be so Linux focused. I suspect it could be a great option for
people (like myself) who must do development under both platforms and want
to create a common build/packaging processes. For my first attempt, I'm not
as interested in a full QNX image as selectively building several
middle-ware components that are very portable (mostly 'C' code only - no
strict Linux dependencies).

So far I've examined the Linaro and Code Sourcery toolchain meta-layers.
I've tried to to implement my own QNX tool-chain but it's not clear if it's
possible to selectively apply this to specific recipes. I've found
instructions here for OE:

http://www.openembedded.org/wiki/Adding_a_secondary_toolchain

but these seems significantly different from the approaches I've seen
implemented for Linaro and Code Sourcery. Which one is the correct approach
. . . will they both work under Yocto? Also, QNX is *not* eglibc based (it
uses Dinkumware C/C++ libraries) so I'm not sure how that might impact the
layer. Likewise there are no Linux headers, etc... Also, it's not real
clear on how to "enable" this external tool-chain and if it can be done
selectively per recipe. I've been racking my brain on this topic. Any
helpful guidance would be appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20130619/be8bc842/attachment.html>


More information about the yocto mailing list