[OE-core] Add LAPACK/ATLAS/BLAS library to OE-CORE

[david bensoussan]

Hello,
Sorry for the long mail, it is my first one to the mailing list.
I am working with a raspberrypi 3 since some time and some packages I work
with on ROS (e.g cartographer) need ATLAS library and its dependencies.

This library cannot be cross compiled as precised in Q3 here
<http://www.vesperix.com/arm/atlas-arm/faq/index.html>.
I was thinking of creating recipes for all of them and make a PR in meta-oe.

Since the .a and .so cannot be compiled by Yocto and varies for each
architecture, I can compile them on the target hardware and provide them in
the recipe afterwards. I was thinking of including them as:
libblas-raspberrypi3.a, libatlas-raspberrypi3.a etc.

And in the recipe, having empty configure and compile steps and in the
install, lines as:
install -m 0644 ${WORKDIR}/libblas-${MACHINE}.a ${D}${libdir}/libblas.a

The recipe would also include a COMPABILE_MACHINE tag to warn users of
recipe limitations.
The advantage is everyone would be able to add its own machine and it will
not break.

What do you think of this? Should I go for it this way?

Thanks,
Regards,
David Bensoussan - Synapticon
-- 

*David bensoussan*
Roboticist / Embedded Software Engineer
------------------------------

*Synapticon* | Robotic Control Systems
Mobile: 004915779804515 / 0033659971070
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170424/57e3365a/attachment-0002.html>