i was thinking of doing this but i don't know my m4.

would be nice if it automatically looked for the path of the gschema-compiler in the pkgconfig file, etc.

any support should also include a rule that attempts to build the schema file in the 'make all' rule before 'make install' installs a potentially broken file.

The --one-schema-file and --dry-run options in that other bug could be very useful for that 'attempt to build'

I've committed support for --one-schema-file and --dry-run now

Created attachment 159245 [details] [review]
Allow passing multiple schemas to gschema-compile

To make test suites easier to implement

Created attachment 159246 [details] [review]
Add GSettings macros helper

When those 2 patches get in, I'll modify the porting guide to take that into account.

-  if (one_schema_file)
+  if (schema_files)
     {
-      g_ptr_array_add (files, one_schema_file);
+      guint i;
+      for (i = 0; i < g_strv_length (schema_files); i++)
+        g_ptr_array_add (files, schema_files[i]);
     }

That seems redundant, since schema_files is already a NULL-terminated array...
You could just use build the ptrarray only in the !schema_files case, and assign schema_files = g_ptr_array_free (files, FALSE), and then use that instead of |files->pdata| in the parse_gschema_files call.

Created attachment 159248 [details] [review]
Allow passing multiple schemas to gschema-compile

To make test suites easier to implement

Comment on attachment 159248 [details] [review]
Allow passing multiple schemas to gschema-compile

Please commit

Comment on attachment 159246 [details] [review]
Add GSettings macros helper

Committed a slightly different version with recent pkg-config changes

Porting guide updated as well. All done!