Re: GSettings and you

[Bastien Nocera <hadess hadess net>]

On Wed, 2010-04-21 at 10:48 +0100, Richard Hughes wrote:
> On 21 April 2010 09:26, Richard Hughes <hughsient gmail com> wrote:
> > Although we obviously need a cleaner solution than that.
> 
> I've just done:
> 
> diff --git a/configure.ac b/configure.ac
> --- a/configure.ac
> +++ b/configure.ac
> @@ -170,8 +170,6 @@ fi
> 
>  AC_PATH_PROG(GCONFTOOL, gconftool-2)
>  AM_GCONF_SOURCE_2
> -AC_SUBST(gsettingsschemadir,
> -       `pkg-config --variable gsettingsschemadir gio-2.0`)
>  AC_SUBST(gsettingsupdateschemacache,
>         `pkg-config --variable gsettingsupdateschemacache gio-2.0`)
> 
> diff --git a/data/Makefile.am b/data/Makefile.am
> --- a/data/Makefile.am
> +++ b/data/Makefile.am
> @@ -29,6 +29,7 @@ $(service_DATA): $(service_in_files) Makefile
>         @sed -e "s|\ servicedir\@|$(bindir)|" $< > $@
> 
>  gsettingsschema_DATA = org.gnome.ColorManager.gschema.xml
> +gsettingsschemadir = $(datadir)/glib-2.0/schemas
>  org.gnome.ColorManager.gschema.xml: gnome-color-manager.schemas
>         gsettings-schema-convert --force --gconf --xml --schema-id
> $(@:.gschema=) $< -o $@
>  # --allow-any-name should be removed once the move from gconf is complete
> 
> 
> And this seems to work just fine.

It's wrong if your glib is installed in a prefix different from the one
you're installing your application to, just like GConf was broken if you
didn't install your app in the same prefix as GConf.