Thanks
On Thu, 21 Jul 2016, 23:33 Brad King wrote:
> On 07/18/2016 06:53 PM, Tom Kulaga wrote:
> > I'll try and get together a minimal example to highlight the difference.
>
> This has now been reported with additional information here:
>
>
On 07/18/2016 06:53 PM, Tom Kulaga wrote:
> I'll try and get together a minimal example to highlight the difference.
This has now been reported with additional information here:
https://gitlab.kitware.com/cmake/cmake/issues/16209
We will have to revert the offending changes until another
I'll try and get together a minimal example to highlight the difference.
On Tue, 19 Jul 2016 at 03:16 Brad King wrote:
> On 07/15/2016 04:50 AM, David Callu wrote:
> > 2016-07-15 1:54 GMT+02:00 Tom Kulaga:
> >> I'm using 3.5.2 for a qt based project and I've updated to
On 07/15/2016 04:50 AM, David Callu wrote:
> 2016-07-15 1:54 GMT+02:00 Tom Kulaga:
>> I'm using 3.5.2 for a qt based project and I've updated to 3.6 and the RCC
>> feature
>> seems to fail. Here's a summary
>> When I swtiched to 3.6, the compiler can no longer link to the generated rcc
>> files.
Should this have changed in 3.6 I couldn't see anything in the change log?
How can I control where they are generated?
On Fri, 15 Jul 2016, 18:51 David Callu wrote:
> Hi Tom,
>
> Same thing on my side. I call in my code functions defined in generated
> .cpp from moc/rcc.
Hi Tom,
Same thing on my side. I call in my code functions defined in generated
.cpp from moc/rcc.
Functions name are based on file path used during .cpp generation.
And this path change from cmake 3.5 to 3.6.
You should check functions in generated .cpp files that you used in your
code.
HTH
Hi All,
I'm using 3.5.2 for a qt based project and I've updated to 3.6 and the RCC
feature seems to fail. Here's a summary
CMAKE settings:
cmake_policy(SET CMP0015 NEW) # relative linker paths
cmake_policy(SET CMP0020 NEW) # linking to qmainlib
# Tell CMake to run moc when necessary: