[meta-freescale] [meta-fsl-arm] libmcc sysroot issues

[Otavio Salvador]

Hello,

(added people which may be interested on Cc)

I have prepared a set of patches which I think improves this.

On Mon, Jan 5, 2015 at 5:12 PM, Petr Kubizňák <kubiznak.petr at elnico.cz> wrote:
> I'm experiencing sysroot issues with the libmcc library on the latest
> revision of branch dizzy (2014-12-30, commit
> 7539a694f3d01f1ab5162bfee16b0327f827c4f7). Not all required files are
> populated into the SDK, so the library cannot be further used in the
> application development without manually manipulating the sysroot.
>
> First of all, compilation of such application fails on the dependency on
> <linux/mvf_sema4.h> include file, coming from <linux/mcc_config.h>. The
> mvf_sema4.h file is a part of linux-timesys (3.0.15) kernel (directory
> include/linux), and should be located in /usr/include/linux in the SDK
> sysroot. I wanted to create a patch, but did not find an automated solution
> (as I already described at https://community.freescale.com/message/466383).
> This issue is not just my case, as you can find for example at the following
> link:
> http://developer.toradex.com/how-to/colibri-vf61-real-time-demo-%28xy-pen-plotter%29#Building_the_Qt_User_Interface

Fixed. See below.

> Second (after fixing the first issue manually), linking of such application
> fails on "-lmcc" flag, as it cannot locate libmcc.so library. In sysroot's
> /usr/lib, there is only libmcc.so.1.0, but a libmcc.so link is missing.
> After creating the link manually, the application can build and run as
> expected.

Fixed. See below.

> I would like to ask for a patch of these two issues, or at least for
> pointing me to some *brief* resource where I might learn how to create the
> patch on myself (i.e. what meta-data say yocto how to generate sysroots).
> Sorry, but studying the whole yocto documentation is just too long run. I
> spent whole day trying to find a solution with no success.

I prepared patches for kernel-module-mcc to build fine on master and
also the libmcc symlink issue.

The headers I fixed adding the module headers in the libmcc-dev
rdepends so it is included along the library.

For testing purposes, please check the dizzy-next or master-next
branch and add to your local.conf:

----
TOOLCHAIN_TARGET_TASK_append = ' \
    libmcc-dev \
'
----

After that, do:

bitbake core-image-base -c populate_sdk

and this should work fine.

Specially the mcc_config.h change would be good to have Timesys
engineers to comment and ack it. As it may have impact to other users.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750