[meta-freescale] I think I am missing some critical link, but am lost trying to find it.

Stephen Munnings Stephen.Munnings at nuvation.com
Thu Jun 26 08:45:22 PDT 2014

-----Original Message-----
From: otavio.salvador at gmail.com [mailto:otavio.salvador at gmail.com] On Behalf Of Otavio Salvador
Sent: Thursday, June 26, 2014 11:29 AM
To: Stephen Munnings
Cc: Daiane Angolini; meta-freescale at yoctoproject.org
Subject: Re: [meta-freescale] I think I am missing some critical link, but am lost trying to find it.

On Thu, Jun 26, 2014 at 12:22 PM, Stephen Munnings <Stephen.Munnings at nuvation.com> wrote:
> Have attached (an edited version) of the recipe here.
> Nothing that should affect operations has been changed other than the svn repository paths.
> The sysroots soft link is so that system #include files can be referenced.

The symbolic link is a workaround I'd better fix the build system to avoid it; anyway the culprit seems to be your override in OVERRIDES setting. This is very internal to the Yocto Project metadata and you need to be careful when messing up with it.

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
-----End Original Message-----

Hi Otavio,

Thanks for the assistance.
The symbolic link is OUR workaround, because of the way we structured our .pro file (and the directory hierarchy) on the original development host.
We decided to reference the sysroot from a symbolic link at the next directory level up, and coded it so in the project.  (And created the syslink in both environments)
I don't think you need to do anything about it in the build system.
In other words, it is OUR hack, we are not proud of it, but it helps things stay consistent in our environment.

I have perhaps messed up the OVERRIDES, because the documentation seems rather sparse.
The Yocto manual refers one to the bitbake manual, and the bitbake manual gives some rather elementary examples.
(And no caveats in either manual)

I suspect from your comment, and further reflection that our line should instead have been:
(I think I inadvertently wiped out all other override values in the variable)

Stephen Munnings 
Sr. Design Engineer | 519.594.0976 

More information about the meta-freescale mailing list