summaryrefslogtreecommitdiff
path: root/m4/ax_compiler_flags_gir.m4
Commit message (Collapse)AuthorAgeFilesLines
* switch gnu.org sites to httpsMike Frysinger2017-02-081-2/+2
|
* ax_compiler_flags_*: fix underquoting causing infinite recursionSimon McVittie2016-10-011-2/+2
| | | | | | | | | | | | | | | | | | | | | These macros would fail with infinite recursion if used twice for the same variable, for example AX_COMPILER_FLAGS_CFLAGS([WARN_CFLAGS], ... some options ...) AX_COMPILER_FLAGS_CFLAGS([WARN_CFLAGS], ... more options ...) In particular, invoking AX_COMPILER_FLAGS, followed by AX_COMPILER_FLAGS_CFLAGS with more "yes" options has this failure mode. This is because the first time through the macro, we define ax_warn_cflags_variable = "WARN_CFLAGS" as expected. The second time, because the first parameter is underquoted, its value is substituted before calling m4_define, so we inadvertently define WARN_CFLAGS = "WARN_CFLAGS". The next time WARN_CFLAGS is mentioned, attempts to expand it will recurse forever, because m4 does not special-case a macro that appears in its own expansion like cpp does. Signed-off-by: Simon McVittie <smcv@debian.org>
* ax_compiler_flags: Eliminate ‘minimum’ and ‘maximum’ warning levelsPhilip Withnall2015-02-231-14/+6
| | | | | | | | | | | | These went against the whole concept of providing a baseline set of warnings which is set by the module maintainer, since it allowed individual developers to opt out of certain classes of warning. Remove them, leaving the ‘no’, ‘yes’ and ‘error’ levels. This maintains API compatibility of the macros by marking various EXTRA-* variables as unused, but still handling them, and merging their values with the preceding EXTRA-* variables. For example, all extra ‘maximum’ and ‘error’ flags are now included in the ‘yes’ level of warnings.
* AX_COMPILER_FLAGS_GIR: strip trailing whitespacePeter Simons2015-02-041-2/+2
|
* Re-format AX_COMPILER_FLAGS_* into canon and bump the #serial numbers.Peter Simons2015-01-261-5/+5
|
* ax_compiler_flags_gir: Add a compiler flags macro for g-ir-scannerPhilip Withnall2015-01-261-0/+68
| | | | | | | | | | g-ir-scanner is a tool used within a lot of GNOME projects to generate introspection data from C APIs. It has a couple of warning flags (and is not likely to gain any more in the future), and chaining them to --enable-compile-warnings would be useful. Integrate AX_COMPILER_FLAGS_GIR into AX_COMPILER_FLAGS so that it’s enabled by default.
* remove m4 submoduleDustin J. Mitchell2009-08-011-6/+0
|
* m4: update reference to macro branchPeter Simons2009-08-011-5/+5
|
* m4: update reference to macro branchPeter Simons2009-07-311-7/+5
|
* m4: update reference to macro branchPeter Simons2009-07-301-5/+7
|
* m4: update reference to macro branchPeter Simons2009-07-271-5/+5
|
* Avoid non-ASCII characters in m4 files.Peter Simons2009-07-271-7/+5
|
* m4: update reference to macro branchPeter Simons2009-07-221-7/+6
|
* m4: update reference to macro branchPeter Simons2009-07-211-5/+8
|
* m4: update reference to macro branchPeter Simons2009-07-211-7/+5
|
* m4: update reference to macro branchPeter Simons2009-07-211-6/+6
|
* m4: update reference to macro branchPeter Simons2009-07-201-5/+7
|
* m4: update reference to macro branchPeter Simons2009-07-191-7/+5
|
* m4: update reference to macro branchPeter Simons2009-07-171-6/+6
|
* m4: update reference to macro branchPeter Simons2009-06-231-12/+6
|
* m4: update reference to macro branchPeter Simons2009-06-221-6/+12
|
* m4: update reference to macro branchPeter Simons2009-06-161-5/+7
|
* m4: update reference to macro branchPeter Simons2009-06-101-7/+5
|
* m4: update reference to macro branchPeter Simons2009-06-101-6/+6
|
* m4: update reference to macro branchPeter Simons2009-06-051-7/+6
|
* maint: added initial version of the toolchainPeter Simons2009-05-051-0/+9
The build process requires python, the python StringTemplate module, and preferably SCons. A make-based build exists, but it is really slow and awkward, compared to the SConstruct file.