| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
| |
Some people who don't want gtk-doc also don't want
gobject-introspection, and this helps them.
Tested-by: Ross Burton <ross.burton@intel.com>
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
| |
Pretend to be very new so modules won't bomb out for a too-old
version.
|
| |
|
|
| |
Otherwise we may fail if the user appended with +=
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
We need at least the --enable options to ensure we generate compatible
configure scripts.
|
| |
|
