Hello, I pushed following updates:
commit b74e5e690d8d4e149ea9de3f0fcca37bad93935f (HEAD, yocto/dizzy, for-dizzy) Author: Max Krummenacher <[email protected]> Date: Wed Jan 7 20:43:23 2015 +0100 libmcc: build with versioned soname This adds a versioned soname to the shared library during linking. Otherwise an application linked with '-lmcc' needs libmcc.so for execution, having libmcc.so.1 would not be enough. root@colibri-vf:~# ls -l /usr/lib/libmcc.so* lrwxrwxrwx 1 root root 13 Jan 7 2015 /usr/lib/libmcc.so.1 -> libmcc.so.1.0 -rwxr-xr-x 1 root root 5252 Jan 7 2015 /usr/lib/libmcc.so.1.0 root@colibri-vf:~# mcc-pingpong mcc-pingpong: error while loading shared libraries: libmcc.so: cannot open shared object file: No such file or directory Additionaly the following warning no longer appears. WARNING: QA Issue: mcc-pingpong requires libmcc.so, but no providers in its RDEPENDS [file-rdeps] Signed-off-by: Max Krummenacher <[email protected]> Signed-off-by: Otavio Salvador <[email protected]> commit bd85d15a2466e15b68ab1efb4b61053d26a2ecda Author: Otavio Salvador <[email protected]> Date: Tue Jan 6 12:21:49 2015 -0200 libmcc: Add runtime dependency for kernel-module-mcc-dev The kernel-module-mcc-dev brings the kernel API headers used when doing application development which uses the libmcc. So when libmcc-dev is included in a SDK, this brings all the necessary boilerplate code. The motivation for this can be found at message from Petr Kubizňák <[email protected]>[1]. 1. https://lists.yoctoproject.org/pipermail/meta-freescale/2015-January/012144.html Change-Id: Icd8311c79a87500c0a9d97d9b63fb0340a5908a1 Reported-by: Petr Kubizňák <[email protected]> Signed-off-by: Otavio Salvador <[email protected]> commit f706698db3cdbb959837136255bf6557e89e1927 Author: Otavio Salvador <[email protected]> Date: Tue Jan 6 12:06:45 2015 -0200 libmcc: Fix symbolic link for dynamic library This fixes the Makefile to properly generate the symlink inside the installation directory. Change-Id: I18ad51c87f64780bfdd8bd70abdda5554439d9e8 Reported-by: Petr Kubizňák <[email protected]> Signed-off-by: Otavio Salvador <[email protected]> commit 61aeebb34b1eaf0b10674e27378dd1e012b79cba Author: Otavio Salvador <[email protected]> Date: Tue Jan 6 13:43:35 2015 -0200 kernel-module-mcc: Only include mvf_sema4.h if building in kernel When mcc_config.h is used to make application we shouldn't include mvf_sema4.h as it is an internal symbol of kernel and shouldn't be directly referenced by user space applications using the MCC interface. This allows for application developers to use the SDK without having to copy the 'mvf_sema4.h' header byhand. More detailed information at: https://lists.yoctoproject.org/pipermail/meta-freescale/2015-January/012144.html Change-Id: I39a519d10a15b951c573007d3cf689f32aac3f30 Reported-by: Petr Kubizňák <[email protected]> Signed-off-by: Otavio Salvador <[email protected]> Regards, -- 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 -- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
