summaryrefslogtreecommitdiff
path: root/gtkdocize.in
Commit message (Collapse)AuthorAgeFilesLines
* Fix handling of --srcdirOwen W. Taylor2016-08-271-4/+11
| | | | | | The handling of --srcdir in the last patch a) didn't actually change where configure.ac was found b) didn't actualy let the --srcdir argument through because it was rejected by later code. Fix both.
* Add --srcdir argument to gtkdocizeEmmanuele Bassi2016-06-061-2/+23
| | | | | | | | | Since commit 1401aebc625dd1c7c39457d3455dce3019ded0be gtkdocize in gtk-doc, gtkdocize supports a --srcdir argument, which allows to specify the source directory for non-srcdir builds. The gtkdocize in gtk-doc-stub should support the same argument. See also: https://bugzilla.gnome.org/show_bug.cgi?id=692367
* gtkdocize.in: ensure that m4 directory existsAndreas Müller2014-09-301-0/+1
| | | | | | | | | | | | | Some packages set AC_CONFIG_MACRO_DIR without shipping macros. These end up in errors like | ln: target 'm4/' is not a directory: No such file or directory | cp: cannot create regular file 'm4/': Not a directory Note: This error does not occure e.g when libtoolize is run before because it creates macro directory. Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
* Move gtk-doc-make to ${datadir}/gtk-doc-devel/baserock/morphColin Walters2012-01-111-3/+3
| | | | | | OSTree's build process wants to auto-detect everything in ${datadir}/gtk-doc/ as documentation, but this clearly breaks if the gtk-doc makefile is in there too. Let's just move it.
* gtkdocize: Increase version to 1.1000Colin Walters2012-01-031-1/+1
| | | | | Pretend to be very new so modules won't bomb out for a too-old version.
* Initial versionColin Walters2011-12-311-0/+124