Hi Paul,
Thank you for your help.
replacing
IMAGE_INSTALL += "libgomp libgomp-dev libgomp-staticdev"
with
IMAGE_INSTALL_append = " libgomp libgomp-dev libgomp-staticdev"
in local.conf seems to do the trick, the library is now part of the
target image.
Regards,
Christophe
On 21.04.2015 12:12, Paul Eggleton wrote:
Hi Cristophe,
On Monday 20 April 2015 13:15:06 Christophe Coutand wrote:
Is there a way to include the openmp library on the target image? when
building the full target image for a freescale processor, I get gcc etc...
installed on the target filesystem but not libgomp. It is however correctly
deployed when installing the SDK on the host machine.
The library is packaged in a package called libgomp, headers are in a package
called libgomp-dev. You can add these to your image if you are looking to
build things on the target itself [1], but if you are simply building an
application that you want to link to this library from within the build
system, you should not need to explicitly add it because the build system will
pick up on the dynamic link and add a dependency from your application package
on the libgomp package automatically.
Cheers,
Paul
[1]
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
