On 28/08/17 12:59, Aleksander Morgado wrote:
> Remove the need to run `gtkdocize' when building from git; this should
> be an operation done by the maintainer when modernizing the gtk-doc
> setup (think of e.g. gettextize), no need to do it unconditionally.
>
> This makes it easier for platforms w
> On 07 September 2017 at 08:32 Aleksander Morgado
> wrote:
>
> > Not sure if this is similar/same, but I have the same sort of issue when
> > enabling introspection (which I now need) and cross-compiling - discussed
> > here back in March.
> > I'm moving over now to using a stable release (i
> Not sure if this is similar/same, but I have the same sort of issue when
> enabling introspection (which I now need) and cross-compiling - discussed
> here back in March.
> I'm moving over now to using a stable release (i.e. tarball), but it would be
> useful to have the option to use git chec
> On 06 September 2017 at 20:18 Dan Williams wrote:
>
> On Mon, 2017-08-28 at 12:59 +0200, Aleksander Morgado wrote:
>
> > Remove the need to run `gtkdocize' when building from git; this
> > should
> > be an operation done by the maintainer when modernizing the gtk-doc
> > setup (think of e.g.
On Mon, 2017-08-28 at 12:59 +0200, Aleksander Morgado wrote:
> Remove the need to run `gtkdocize' when building from git; this
> should
> be an operation done by the maintainer when modernizing the gtk-doc
> setup (think of e.g. gettextize), no need to do it unconditionally.
>
> This makes it easi
Remove the need to run `gtkdocize' when building from git; this should
be an operation done by the maintainer when modernizing the gtk-doc
setup (think of e.g. gettextize), no need to do it unconditionally.
This makes it easier for platforms without gtk-doc to build from git.
When trying to build
