This bug was fixed in the package cmake - 3.5.0-1ubuntu3
---
cmake (3.5.0-1ubuntu3) xenial; urgency=medium
* Fix FindPkgModules.cmake (LP: #1563548)
seems that a typo was preventing the correct internal variables from being
set.
-- Gianfranco Costamagna Wed, 30 Mar 2016
00:
** Changed in: cmake (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to cmake in Ubuntu.
https://bugs.launchpad.net/bugs/1563548
Title:
CMake 3.5's pkg-config support broken
To manage notifications
please followup on
https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1563580
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to cmake in Ubuntu.
https://bugs.launchpad.net/bugs/1563548
Title:
CMake 3.5's pkg-config support broken
To manag
yes, it was enough, and the patch was already upstreamed.
https://anonscm.debian.org/cgit/pkg-cmake/cmake.git/commit/?id=b71943bca4ed372568050d460960764ca2b3d4aa
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to cmake in Ubuntu.
https://bugs.la
Only variables started with the passed prefix (in this case `GLIB2`)
should be set. I don't think the variables starting with `glib-2.0_`
should be set.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to cmake in Ubuntu.
https://bugs.launchpad.n
the package is building on my ppa
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu
/costamagnagianfranco-ppa
BTW I honestly think this was a typo in the set variable.
Probably a change like
+- _pkgconfig_set("${_pkg_check_modules_pkg}_${variable}"
"${${_pkg_check_modules_pkg}_
Just confirming that the 3.5.0-1ubuntu2 upload doesn't help
unfortunately.
Note cmake-extras needs to be rebuilt again (no-change) if cmake will
get reverted (yes, we need to come up with some better packaging there -
at least appropriately versioned dependencies on cmake).
--
You received this
This is fallout from a post-beta merge of a new upstream version of
cmake.
A feature freeze exception of a core build tool is altogether
unreasonable. When it introduces regressions, it is unacceptable.
I have communicated to Michał and Gianfranco on IRC that if this issue
is not resolved by my
