[meta-freescale] Qt build in fsl yocto (dora) not making use of environment variables

[Stephen Munnings]

>From: Stephen Munnings 
>Sent: Tuesday, August 12, 2014 12:04 PM
>Subject: Qt build in fsl yocto (dora) not making use of environment variables
>
><snip>,
></snip>
>
>Does anybody have any clues on what might be happening here?
>
>Why are the environment variables not being used?
>

As a follow up to this...
The environment variables are available to the recipe that builds this app since the recipe line:
    echo "Environment vars" ${GDBVERSIONMAJOR} ${GDBVERSIONMINOR} ${GDBVERSIONBUILD} "End env vars"
produces the expected results in the log.
This line is in  a custom task inserted after do_patch and before do_compile.
The qt application build is taken care of (automatically) by having these lines in the recipe:
inherit qmake5
require recipes-qt/qt5/qt5.inc

So the question is "why are these environment variables are available to the recipe, but not to the qmake or make steps?"

I assume from the lack of response that one of the following conditions exists:
1.  The answer is blindingly obvious to everyone but me (I am experiencing a "brain fart")
2.  Nobody else has tried something like this, and thus has no experience to share.
3.  Nobody has a clue what is happening (maybe because I did not give enough information) and therefore has no response.
4. The situation seems so ludicrous as to be nigh impossible, so nobody has any helpful advice to share.

Whatever the case, it seems exceedingly strange that environment variables are seen by yocto/bitbake recipes, but not by the qmake or make steps of a Qt application build they invoke.
(unless there is something that deliberately scrubs the environment - like bitbake does - and I am not aware of it)

Is there any more information I could supply to help figure this out?

--
Stephen Munnings
Sr. Design Engineer | 519.594.0976
www.nuvation.com