Re: Documentation for build system setup

One more question:

The sample on also explicitly calls aclocal 
like this:

aclocal --install || exit 1

But the man page for autoreconf says that autoreconf also calls aclocal, is this redundant? If so, can it be 

On 09/02/17 14:57, Sebastian Geiger (Lanoxx) wrote:
What confuses me is that this paragraph starts with the phrase "it does
not need any modifications made".

It does not need any modifications made, unless you need to run
another tool before configure, or do not use one of glib-gettextize,
gtkdocize or intltoolize. (Note that you should not use both
glib-gettextize and intltoolize in the same module, and it is better
to use neither; see the FAQ entry below for details.) 
It might be more helpful to provide a listing that omits both
glib-gettextize and intltoolize and then add a paragraph explaining to
add these for project that use either of these tools. If I understand
right both a deprecated anyway and should not be needed for
state-of-the-art projects.

Maybe write something like this:

If you are still using the deprecated glib-gettextize, then add the following line immediately before

    glib-gettextize --force --copy || exit 1

If you are still using the almost obsolete intltoolize, then add the following line immediately before

    intltoolize --force --copy --automake || exit 1

On 09/02/17 11:45, Philip Withnall wrote:
Can we please standardise on the given in ?

It does everything we need, and meets all the standards (like build-
api). If you’ve got improvements to make, please make them on that

Sebastian: the paragraph immediately above the example does say that
you should remove one or both of the intltoolize/glib-gettextize calls
as appropriate.

desktop-devel-list mailing list
desktop-devel-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]