On Thu, Jul 9, 2015 at 12:12 PM, Cody P Schafer <[email protected]> wrote:
> On Thu, Jul 9, 2015 at 12:06 PM, Cody P Schafer <[email protected]> wrote:
>> Without this, Qt5LinguistTools/Qt5LinguistToolsConfig.cmake would
>> attempt to locate lrelease and lupdate under prefix, even while we were
>> cross-compiling and prefix points at the native system's root dirs.
>>
>> Signed-off-by: Cody P Schafer <[email protected]>
>> ---
>>  recipes-qt/qt5/qttools-native_git.bb               |  5 +++-
>>  ...ols-cmake-allow-overriding-the-location-f.patch | 30 
>> ++++++++++++++++++++++
>>  recipes-qt/qt5/qttools_git.bb                      |  1 +
>>  3 files changed, 35 insertions(+), 1 deletion(-)
>>  create mode 100644 
>> recipes-qt/qt5/qttools/0004-linguist-tools-cmake-allow-overriding-the-location-f.patch
>
> On second thought, I'm not quite sure this is the right solution.
>
> It appears the core of the issue is that cmake_qt5 is pulling in the
> Qt5LinguistTools cmake from the target sysroot, when it should really
> be using the native sysroot.
>
> Does anyone have pointers on the "right" way to handle cmake files and
> cross compilation?

After a bit more digging, it appears the issue I'm having is that
sometimes the .cmake in the native sysroot is used, and sometimes the
.cmake in the target (beaglebone, in my case) sysroot is used.

And the beaglebone one doesn't work (probably expected).

And this patch doesn't actually work: my build appears to have only
succeeded due to selecting the functional cmake file.
-- 
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Reply via email to