Thanks for that Pete.
>From the build log, I think the issue is simply that gtest changed, and
we need to pull in your cmake fixes. I think we have those in devel
already, but not released yet. I’ll figure it out on Monday :)
> On 13 Jan 2017, at 21:09 , Pete Woods <1656...@bugs.launchpad.net> wrote:
> There seems to be some weirdness with Qt5.7 messing with build flags.
> For indicator-network, where we have C++14 enabled, Qt seemed to be
> inserting -std-c++11 (or whatever the exact flag is) in addition.
> Switching to the new set(CMAKE_CXX_STANDARD 14) and set(CMAKE_C_STANDARD
> 11) seemed to resolve it.
> You received this bug notification because you are subscribed to unity-
> scopes-api in Ubuntu.
> unity-scopes-api FTBFS with Qt 5.7.1
> Status in unity-scopes-api package in Ubuntu:
> Bug description:
> As part of test building Qt reverse dependencies, it was found unity-
> scopes-api fails to build (at least) when built against Qt 5.7.1 on
> As unity-scopes-api continues to work without a rebuild, it's not a
> blocker for Qt 5.7.1 transition but should be fixed for the next
> Log: https://launchpadlibrarian.net/301312233/buildlog_ubuntu-zesty-
> To manage notifications about this bug go to:
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
unity-scopes-api FTBFS with Qt 5.7.1
To manage notifications about this bug go to:
ubuntu-bugs mailing list