summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* version 3.14.03.14.0David King2014-09-221-1/+1
|
* macros2: Update links to macros in the autoconf-archivePhilip Withnall2014-09-152-2/+2
| | | | | Now that the macros have been committed upstream, we can link to their manual pages rather than the bug reports.
* macros2: Add support for APPSTREAM_XML macroBastien Nocera2014-09-111-0/+4
| | | | | | And request that appstream-xml.m4 get installed if missing. https://bugzilla.gnome.org/show_bug.cgi?id=736497
* macros2: Deprecate GNOME_CODE_COVERAGEPhilip Withnall2014-08-283-130/+188
| | | | | | The autoconf-archive AX_CODE_COVERAGE macro should be used instead. https://bugzilla.gnome.org/show_bug.cgi?id=729405
* macros2: Deprecate GNOME_MAINTAINER_MODE_DEFINESPhilip Withnall2014-08-281-2/+4
| | | | | | | | | | | | The modules which it deprecates are all ancient and unused. Many of the modules which use GNOME_MAINTAINER_MODE_DEFINES don’t make use of the DISABLE_DEPRECATED variable it generates anyway. If a module really wants maintainer mode, they should use AM_MAINTAINER_MODE. Otherwise, they should just eliminate this call entirely. https://bugzilla.gnome.org/show_bug.cgi?id=735417
* macros2: Deprecate GNOME_DEBUG_CHECKPhilip Withnall2014-08-283-13/+130
| | | | | | | | The autoconf-archive AX_DEBUG_CHECK macro should be used instead, or the macro contents should just be substituted into configure.ac directly, since it’s so simple. https://bugzilla.gnome.org/show_bug.cgi?id=729403
* build: Remove a non-existent file from EXTRA_DISTPhilip Withnall2014-08-261-1/+0
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=735418
* compiler-flags: allow suppressing warningsMichael Catanzaro2014-08-181-1/+1
| | | | | | | | | | Some projects want to see no warnings at all, for example, projects that are written in Vala. But GNOME_COMPILE_WARNINGS([no]) is a no-op that does nothing to turn off the default compiler warnings. Presumably if you ask for no compiler warnings, you want no compiler warnings, so suppress them in this case instead. https://bugzilla.gnome.org/show_bug.cgi?id=734973
* code-coverage: Support lcov 1.11Martin Pitt2014-07-101-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=732988
* macros2: Remove FORBIDDEN_M4MACROS infrastructurePhilip Withnall2014-05-131-28/+0
| | | | | | | It was completely outdated and unused. The REQUIRED_M4MACROS infrastructure is, however, still in use. https://bugzilla.gnome.org/show_bug.cgi?id=729932
* macros2: Remove outdated README filePhilip Withnall2014-05-021-13/+0
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=729410
* doc: Move doc/usage.txt to README and updatePhilip Withnall2014-05-021-13/+11
| | | | | | | We don’t like references to CVS any more. Update the guidelines to no longer reference GNOME_COMMON_INIT. https://bugzilla.gnome.org/show_bug.cgi?id=729410
* make program_VERSION a local variableAntoine Jacoutot2014-04-151-0/+1
| | | | | Otherwise we may end up overriding what was manually set in the environment.
* version 3.12.03.12.0David King2014-03-241-2/+2
|
* gnome-autogen.sh: Fix check if stdin is a ttyVolker Sobek2014-03-221-1/+1
| | | | | | | | Commit 7f977b021462 introduced a check if stdin is ins't a tty, and prevent printing terminal codes in this case. But the check was wrong and always failed. https://bugzilla.gnome.org/show_bug.cgi?id=726892
* gnome-autogen: require automake 1.11.2Ryan Lortie2014-03-131-0/+4
| | | | | This is the version of automake that introduced ACLOCAL_PATH support, so make sure that we have it before attempting to configure the package.
* gnome-common: use ACLOCAL_PATH over ACLOCAL_FLAGSRyan Lortie2014-03-121-10/+7
| | | | | | jhbuild has set this variable for more than two years. https://bugzilla.gnome.org/show_bug.cgi?id=726208
* gnome-autogen.sh: correct IFS valueRyan Lortie2014-03-121-1/+1
| | | | | | | Due to a likely copy-paste mistake, the default value of IFS was being set to 9 spaces instead of a tab and a space. Fix that. https://bugzilla.gnome.org/show_bug.cgi?id=726208
* gnome-autogen.sh: Check for appdata-xml.m4 with APPDATA_XMLDavid King2013-12-161-0/+4
|
* compiler-flags: Simplify a case statement slightlyPhilip Withnall2013-10-291-4/+1
|
* compiler-flags: Replace deprecated AC_HELP_STRING with AS_HELP_STRINGPhilip Withnall2013-10-291-4/+4
|
* Read the dirlist file unconditionallyJavier Jardón2013-10-011-3/+2
|
* version 3.10.03.10.0David King2013-09-231-1/+1
|
* compiler-flags: Add a #serial linePhilip Withnall2013-09-041-0/+5
| | | | | | | | As suggested in bug #707475, this will ensure the latest version of gnome-compiler-flags.m4 is used if conflicting versions are found in different directories in the autoconf search path. Helps: https://bugzilla.gnome.org/show_bug.cgi?id=707475
* compiler-flags: Add an optional second argument for custom warningsPhilip Withnall2013-09-041-2/+12
| | | | | | | | | This allows module authors to choose to enforce stricter warnings on a per-module basis, to avoid the situation where an outside contributor submits a patch which introduces warnings the maintainer has enabled locally. Closes: https://bugzilla.gnome.org/show_bug.cgi?id=707475
* Run intltool before autoreconf so intltool.m4 is picked up by aclocal.Seán de Búrca2013-08-271-4/+4
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=705365
* gnome-autogen.sh: run glib-gettexize if using GLib gettextJavier Jardón2013-07-221-0/+5
| | | | | This code was removed by error in commit 323bbfe0989405725379cada1aa5cb361fd2999f
* gnome-autogen.sh: Check only for autoreconfJavier Jardón2013-07-191-57/+7
| | | | autoconf, automake, libtool, gettext are already checked by autoreconf
* Rename configure.in to configure.acJavier Jardón2013-07-192-1/+1
|
* gnome-autogen: Do not use sed to get the AC_CONFIG_MACRO_DIR directoryJavier Jardón2013-07-181-1/+1
|
* macros2/gnome-autogen.sh: Create m4 directory if it doesnt exitsJavier Jardón2013-07-181-0/+8
| | | | This is a automake bug fixed in automake 1.13.2
* gnome-autogen.sh: Use autoreconfJavier Jardón2013-07-181-75/+7
| | | | instead autopoint/libtoolize/autoconf/automake manually
* Add support for automake 1.14Yosef Or Boczko2013-06-271-9/+10
|
* code-coverage: fix conditionalizationDan Winship2013-05-081-2/+4
| | | | | | | | | | | The "make clean" rule added by gnome-code-coverage.m4 was not conditionalized (making it spew errors on "make clean" when built without coverage support, since $(LCOV) expanded to ""), and the other rules were conditionalized incorrectly (testing "ifdef CODE_COVERAGE_ENABLED", when that variable was always set, just sometimes to "no"). Fix both problems. https://bugzilla.gnome.org/show_bug.cgi?id=699943
* Add support for lcov 1.10Paolo Borelli2013-04-081-1/+1
|
* version 3.7.43.7.4David King2013-01-141-1/+1
|
* COPYING: add GPL-2 license fileRoss Burton2013-01-101-0/+339
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Finally declare gnome-common to be GPL 2+, by doing some source code archaeology. These files we can effectively ignore: .gitignore AUTHORS ChangeLog.pre-git NEWS README doc-build/README doc/usage.txt gnome-common.doap macros2/README.cvs-commits The build files you could argue are boilerplate/uncopyrightable: Makefile.am autogen.sh configure.in doc-build/Makefile.am macros2/Makefile.am So that leaves: doc-build/gnome-doc-common.in doc-build/omf.make doc-build/xmldocs.make Appeared in e16ea58db92e05b9720acdc6992175ec346dfc91. Appears to have been copy-pasted from scrollkeeper-example2, LGPLv2.1. macros2/gnome-autogen.sh Can be traced back to gnome-libs 88f7376472d3ee54329213c118b46225703d8223, which is GPLv2/LGPLv2. macros2/gnome-code-coverage.m4 LGPLv2.1+. macros2/gnome-common.m4 macros2/gnome-compiler-flags.m4 Synced with gnome-core as of 425e5cc9aad003c9f64d43f2d3f15e04a97db854, so LGPLv2.1+. The long-standing assumption is that gnome-common was GPLv2+, so use that license. Finally the tyranny of unclear licensing is over! https://bugzilla.gnome.org/show_bug.cgi?id=133689
* build: remove useless (empty or ancient) files that we don't needRoss Burton2013-01-103-36/+0
|
* Add support for automake 1.13.Raphael Kubo da Costa2013-01-081-8/+9
|
* Better support of using AUTOCONF environment variableDodji Seketeli2012-12-101-9/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When I launch gnome-autogen.sh by telling it to use a version of autoconf that is at a particular path -- by using the AUTOCONF environment variable -- I can see that there is a spot in the script that fails to honour that variable. I thus get the error message (that I trim to just keep the relevant part): AUTOCONF=/my/autoconf AUTOM4TE=/my/autom4te /bin/sh -x /usr/bin/gnome-autogen.sh [...] +++ find_configure_files /home/dodji/devel/git/gdl/master +++ configure_ac= +++ test -f /home/dodji/devel/git/gdl/master/configure.ac +++ test -f /home/dodji/devel/git/gdl/master/configure.in +++ configure_ac=/home/dodji/devel/git/gdl/master/configure.in +++ test x/home/dodji/devel/git/gdl/master/configure.in '!=' x +++ echo /home/dodji/devel/git/gdl/master/configure.in +++ autoconf -t 'AC_CONFIG_SUBDIRS:$1' /home/dodji/devel/git/gdl/master/configure.in +++ read dir /home/dodji/devel/git/gdl/master/configure.in:8: error: Autoconf version 2.65 or higher is required /home/dodji/devel/git/gdl/master/configure.in:8: the top level autom4te: /bin/m4 failed with exit status: 63 I think the problem is that the find_configure_files function uses 'autoconf' directly instead of using $AUTOCONF. So it's taking the autoconf binary that is in my path, and that one doesn't satisfy the version requirement of the configure.in script template that is in. /home/dodji/devel/git/gdl/master/configure.in. The patch below fixes that essentially by s/autoconf/$AUTOCONF there, and also by moving the definition point of the AUTOCONF variable -- that is done by a call to version_check -- before the first spot that actually uses it. It's worth noting that this bug appears to have been introduced by the patch attached to bug #510713. Tested on my Fedora Rawhide system. * macros2/gnome-autogen.sh (find_configure_files): Use the AUTOCONF variable, rather than calling the autoconf program directly. Remove the now useless comment. (<at global scope>): Move the definition of the AUTOCONF variable before its first use.
* compiler-warnings: Fix tabs->spacesColin Walters2012-11-131-19/+19
| | | | Per https://bugzilla.gnome.org/show_bug.cgi?id=688192
* compiler-warnings: Drop -Wdeclaration-after-statementColin Walters2012-11-121-3/+1
| | | | | | Some GNOME modules want the ability to use C99, let's not hamper them. https://bugzilla.gnome.org/show_bug.cgi?id=688192
* compiler-warnings: Drop -Wno-sign-comareColin Walters2012-11-121-1/+1
| | | | | | | | | | It's not part of -Wall, and we're not explicitly turning it on here, so there's no point in turning it off, since it's not on. Additionally, if a given module did want it on, it's clearer if the compiler flags don't have -Wno-sign-compare -Wsign-compare. https://bugzilla.gnome.org/show_bug.cgi?id=688192
* compiler-warnings: Move -Wnested-externs to the always-on warning setColin Walters2012-11-121-1/+1
| | | | | | Since there's no reason to have it different for yes/maximum. https://bugzilla.gnome.org/show_bug.cgi?id=688192
* compiler-warnings: code cleanup: Extract common warnings into variablesColin Walters2012-11-121-20/+23
| | | | | | Will make future refactoring clearer, and also we have comments now. https://bugzilla.gnome.org/show_bug.cgi?id=688192
* compiler-warnings: Drop -Waggregate-returnColin Walters2012-11-121-2/+0
| | | | | | | | This trips up gnome-desktop using things like XSyncValue, and while it's possible to avoid, we shouldn't punish people who are pushed to use structures as return values by external APIs. Returning a two-element structure is not a big deal.
* compiler-warnings: cosmetic cleanup: Put each warning on own lineColin Walters2012-11-121-2/+25
| | | | So that further patches are more readable.
* Add lots of warnings to GNOME_COMPILE_WARNINGSDavid King2012-11-021-26/+28
| | | | | | | | | | | | | Following Colin Walters' thread on desktop-devel-list: https://mail.gnome.org/archives/desktop-devel-list/2012-July/msg00100.html Add a selection of more strict warnings to the default level of GNOME_COMPILE_WARNINGS. Check all the warnings by passing them to GCC, and ignore those which fail. Set the severity of some of the warnings to errors, so that particularly bad code is rejected (set the warning level to ‘minimum’ is you wish to avoid this behaviour). Fixes bug 568546 and bug 608953.
* code-coverage: Relicence to LGPLv2.1+Philip Withnall2012-10-311-2/+1
| | | | | | | | | | | | As gnome-common is widely used, it’s useful for it to have a fairly liberal licence. This relicences the gnome-code-coverage.m4 file from GPLv3+ to LGPLv2.1+. Permission has been obtained (by private e-mail) from the other contributors: • Christian Persch <chpe@gnome.org> • Xan Lopez <xan@gnome.org> See also: https://bugzilla.gnome.org/show_bug.cgi?id=133689
* code coverage: Quiet lcov and add extra ignore patternsChristian Persch2012-10-231-4/+10
| | | | | Make lcov be quiet if V=0, and add a new CODE_COVERAGE_IGNORE_PATTERN variable to be able to add extra files to ignore in code coverage reporting.
View Lorry Controller Status