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

[Stephen Munnings]

-----Original Message-----
From: otavio.salvador at gmail.com [mailto:otavio.salvador at gmail.com] On Behalf Of Otavio Salvador
Sent: Wednesday, June 25, 2014 2:15 PM
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 Wed, Jun 25, 2014 at 2:37 PM, Stephen Munnings <Stephen.Munnings at nuvation.com> wrote:
> -----Original Message-----
> Where would I find the generated Makefiles?
> I cannot seem to find them.  I even did a "find" on the entire build/ directory, but none of the Makefile matches were for the Qt application.

In the build/tmp/work inside the application directory. QMake will generate them.

PS: if you're using rm_work you won't see them

...
> Is it normal to have to specify the PATH for finding the cross-toolchain when building a Qt application?
> If so, then there is probably nothing wrong here.

No. It is a bug.

You can see for example the recipe we did for qsiv[1] in meta-qt5[2].

1. http://code.ossystems.com.br/gitweb?p=qt%2Fqsiv.git
2. https://github.com/meta-qt5/meta-qt5/blob/master/recipes-qt/qsiv/qsiv_1.1.bb

It is a working example.

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

-----End Original Message-----

Hi Otavio,

Checked your example recipe against our recipe.
Made some (small) changes to ours, needed something in ours that yours does not have:
require recipes-qt/qt5/qt5.inc

Also included the line:
PACKAGE_ARCH = "${MACHINE_ARCH}"

Which causes the files to go into a different directory in /tmp/work/

Still have the same issue.

In the (non-yocto) host development environment, we specify the toolchain (and other things) in the graphical environment using Qt Creator and "Manage Kits", and these settings end up in the .pro.user file.
We do not bring this file into the yocto environment (nor would it be correct in that environment).
Is this likely the source of our problems?

Regards,

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