Hi Dave, hi Jakob,
thank you for the responses to my question.
I finally found "my" solution: It seems that the creators of the cmake
Qt5 toolchain
have created some undocumented hooks:
In Qt5CoreConfigExtras, the moc is specified as an imported target:
>> if (NOT TARGET Qt5::moc)
>>add_exec
On Thu, Dec 17,
>
> So, here is my question: How can I overwrite the moc-executable (and uic
> etc) path to use another moc version than the one found by the
> find_package mechanism? If I use the moc which is part of my Linux host
> PC rather than the arm compiled moc in the Raspberry file system,
Maybe you can do something with the ‘HINTS’ option to find_package()?
https://cmake.org/cmake/help/v3.4/command/find_package.html
Sincerely,
Jakob
> On 17 Dec 2015, at 18:03, Hauke Krüger wrote:
>
> Hi everybody,
>
> I have a project which builds to realize a Qt5 application. I use the
> lates
Hi everybody,
I have a project which builds to realize a Qt5 application. I use the
latest CMAKE Qt5 mechanisms such as AUTOMOC etc with good success.
The project builds on Raspberry Pi if cmake is run on the Raspberry Pi
itself since all Qt tools are available and run also on the Raspberry Pi.
