GSettings add_schema does not work correctly with generated schemas files
Bug #1661686 reported by
dobey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cmake-extras (Ubuntu) |
Fix Released
|
High
|
dobey |
Bug Description
When one needs to generate the final .gschema.xml file from an .in, either for specifying default values at build time, or to enable translations, the GSettings module is not usable, as it only takes the name of the file as an argument, and assumes the file is always in CURRENT_SOURCE_DIR, which is not the case when generating the file and builddir != srcdir.
Related branches
lp:~dobey/cmake-extras/fix-gsettings
- Charles Kerr (community): Approve
- Pete Woods: Approve
-
Diff: 168 lines (+110/-2)7 files modifieddebian/changelog (+7/-0)
debian/tests/control (+10/-0)
debian/tests/gsettings (+53/-0)
examples/gsettings-demo/CMakeLists.txt (+13/-0)
examples/gsettings-demo/generated.gschema.xml.in (+9/-0)
examples/gsettings-demo/static.gschema.xml (+9/-0)
src/GSettings/GSettingsConfig.cmake (+9/-2)
Changed in cmake-extras (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Rodney Dawes (dobey) |
To post a comment you must log in.
This bug was fixed in the package cmake-extras - 1.2+17. 04.20170213- 0ubuntu1
--------------- 04.20170213- 0ubuntu1) zesty; urgency=medium
cmake-extras (1.2+17.
* Add autopkgtest for gsettings macro.
* Handle generated gschema files. (LP: #1661686)
-- Rodney Dawes <email address hidden> Mon, 13 Feb 2017 18:16:40 +0000