[yocto] Porting a middleware to Yocto

[Jussi Kukkonen]

On 11 April 2017 at 09:20, Eswaran Vinothkumar (BEG/PJ-IOT-EL) <
Vinothkumar.Eswaran at de.bosch.com> wrote:

> Hallo,
>
>
>
> For our new project we are planning to use Yocto as a build system to
> build customized Linux distribution. I have already created a BSP for our
> customized hardware with Linux kernel, U-boot and UBIFS rootfs image.
>
>
>
> We are internally using a middleware which acts as an abstraction to
> underlying operating system and provides APIs to application layers. Now
> the task is to port the middleware to Yocto. The middleware contains lot of
> make files and folders which are interdependent and I am at lost on how to
> start.
>
> I have some 20 directories which contains makefiles and autotool
> configure.ac files to generate lib files.
>
>
>
> As of now I have planned to create a new Yocto layer called
> meta-middleware and a recipe file for individual folders. I then create a
> package group which will include all these recipes and can include this
> package group as dependency in the recipes of meta-application layer. I am
> facing a problem like I have to include headers from other recipes. In this
> case to include the headers , is it enough to add “DEPENDS = recipename” ?
>

Yes, a DEPENDS should be all that's needed in the normal case. The
assumption is that the recipe you depend on installs the headers and
libraries like it should -- these will then be made available in the
sysroot of the recipe you are compiling (the location and nature of this
sysroot depends on the version of yocto). If your autotools setup is well
behaving the recipes should be fairly straight forward to write.

If you have issues with not finding headers, start by making sure that the
recipe you depend on installs things correctly: see e.g.
$WORKDIR/sysroot-destdir/ to see files that should become available in the
sysroot of a anyone depending on this recipe. If that looks fine, make sure
the depending project is doing something sane to find the headers (like
using pkg-config): see e.g. $WORKDIR/temp/log.do_configure.

Better advice probably requires you to actually show a problem case and
mention the version of Yocto you are using.

HTH,
  Jussi


> I know my question is relatively vague, but anybody who ported middleware
> from another build systems like ptxdist would have faced similar issues.
> Any input on how you planned to port these source files to Yocto would be
> helpful.
>
>
>
>
>
> Mit freundlichen Grüßen / Best regards
>
>
> *Vinothkumar Eswaran BEG-PT/PJ-IOT1*
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170411/cc5bfd8b/attachment.html>