** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) => Michi Henning (michihenning)
** Changed in: unity-scopes-api (Ubuntu)
Importance: Undecided => Critical
** Changed in: unity-scopes-api (Ubuntu)
Status: New => In Progress
--
You received this bug notification
** Branch linked: lp:~michihenning/unity-scopes-api/merge-devel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656042
Title:
unity-scopes-api FTBFS with Qt 5.7.1
To manage notifications about this
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 :)
Michi.
> On 13 Jan 2017, at 21:09 , Pete Woods
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
We have changes in lp:unity-scopes-api/devel to work with the new
version of googletest/googlemock that haven't been landed on trunk yet.
So fixing this is probably going to be as simple as building a new
release.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
