summaryrefslogtreecommitdiffstats
path: root/meta/recipes-gnome/gtk-doc/files
AgeCommit message (Collapse)Author
2018-09-10gtk-doc: update to 1.29Alexander Kanavin
(From OE-Core rev: 264fc66963d1700f374dd4cfcf107ba2487f4759) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-05-04gtk-doc: update to 1.28Alexander Kanavin
(From OE-Core rev: 22cc8b49e31a121ab48d3ebaae5d0ccfaa4053fa) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-25gtk-doc: don't regenerate gtk-doc in do_installRoss Burton
In out-of-tree builds gtk-doc's setup-build target copies all the content from $srcdir to $builddir. However, if some of this content is regenerated at configure time this can happen: 1) configure writes new build/version.xml 2) make compile copies content, including the tarball's src/version.xml to build/version.xml, and generates gtk-doc. 3) make install notices build/version.xml is older than configure.status, so regenerates gtk-doc. gtk-doc generation is a slow process at the best of times, so doing it twice isn't good. (From OE-Core rev: 9ea9d61f26a942dbbc90070b40ba0209021a4b46) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-11gtk-doc: refresh patchesRoss Burton
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 3277e60b6eefb3a1c858462bc89244f6577dca52) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06gtk-doc: update to 1.27Alexander Kanavin
Gtk-doc has been rewritten in Python, so drop perl dependencies (good riddance!), and adjust patches to reflect that. (From OE-Core rev: f4a00893a4209330720c0366ddde6b9941ee3196) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-06-28gtk-doc: Handle floating gtk-doc dependencyRichard Purdie
Allow the tests to be explicitly disabled to avoid floating dependnecy issues. This is not really an issue with RSS but is on previous releases. Currently the tests are enabled/disabled depending on the presence of glib-2.0. (From OE-Core rev: 6c12d0b8a44a91382d3aa064ebef43769d909e73) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-14gtk-doc: require perl-native only if api-documentation feature is enabledAlexander Kanavin
This should reduce build times. (From OE-Core rev: 74d9c5eb858bfe1dd16826b74be3af71bb1956d9) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09gtk-doc: use pkg-config-native in native gtk-doc.m4Ross Burton
When building gtk-doc-native the m4 functions for autoconf should use pkg-config-native instead of pkg-config so that they can find the native tooling. This means that it is possible to generate gtk-doc without building the target packages. (From OE-Core rev: 755724d9d5f023450392ae8025a0cb6264283028) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09gtk-doc: add a recipe, remove gtk-doc-stubAlexander Kanavin
(From OE-Core rev: 8b958312d360e6692dc7c6dd3d2b2591301f9e59) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>