diff options
| author | Ryan Lortie <desrt@desrt.ca> | 2010-10-26 12:02:12 -0400 |
|---|---|---|
| committer | Ryan Lortie <desrt@desrt.ca> | 2010-10-26 12:02:12 -0400 |
| commit | 9126f1afae922339949d0b76e282411618bcb565 (patch) | |
| tree | e09a5ab9ae8b343cf94e031264f6bd4b24ce821c /m4macros | |
| parent | 181982c47cde49b3aff2293729f5aee5987db8af (diff) | |
gsettings m4: Use --strict for checking
A while ago we allowed glib-compile-schemas to return a 'success' status
in the case that just one schema file contained errors. Of course, this
is the exact opposite of what we want in the case that we are checking
schema validity at compile time.
Use the --strict flag for that case.
This closes #633115.
Diffstat (limited to 'm4macros')
| -rw-r--r-- | m4macros/gsettings.m4 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/m4macros/gsettings.m4 b/m4macros/gsettings.m4 index e81a51241..4e4352fa9 100644 --- a/m4macros/gsettings.m4 +++ b/m4macros/gsettings.m4 @@ -37,7 +37,7 @@ mostlyclean-am: clean-gsettings-schemas gsettings__enum_file = $(addsuffix .enums.xml,$(gsettings_ENUM_NAMESPACE)) %.gschema.valid: %.gschema.xml $(gsettings__enum_file) - $(AM_V_GEN) if test -f "$<"; then d=; else d="$(srcdir)/"; fi; $(GLIB_COMPILE_SCHEMAS) --dry-run $(addprefix --schema-file=,$(gsettings__enum_file)) --schema-file=$${d}$< && touch [$]@ + $(AM_V_GEN) if test -f "$<"; then d=; else d="$(srcdir)/"; fi; $(GLIB_COMPILE_SCHEMAS) --strict --dry-run $(addprefix --schema-file=,$(gsettings__enum_file)) --schema-file=$${d}$< && touch [$]@ all-am: $(gsettings_SCHEMAS:.xml=.valid) uninstall-am: uninstall-gsettings-schemas |