After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 616311 - gschema-compile outputs in current directory
gschema-compile outputs in current directory
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: gsettings
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Allison Karlitskaya (desrt)
gtkdev
Depends on:
Blocks:
 
 
Reported: 2010-04-20 16:26 UTC by Bastien Nocera
Modified: 2010-04-20 21:28 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gschema-compile: output to src dir by default (887 bytes, patch)
2010-04-20 19:39 UTC, Bastien Nocera 		none Details | Review

Description Bastien Nocera 2010-04-20 16:26:36 UTC 
Using the rule:
gsettingsschema_DATA = org.gnome.Bluetooth.gschema.xml
install-data-hook:
        $(gsettingsupdateschemacache) $(gsettingsschemadir)
The gschemas.compiled file ends up in the current directory

Adding " --targetdir=$(gsettingsschemadir)" fixes it.
Comment 1 Bastien Nocera 2010-04-20 19:39:23 UTC 
Created attachment 159190 [details] [review]
gschema-compile: output to src dir by default

Instead of dumping the compiled version in the current directory.
Comment 2 Allison Karlitskaya (desrt) 2010-04-20 21:20:34 UTC 
this bug was introduced by the windows porting; the tool used to chdir() to the schema directory but that was removed...
Comment 3 Allison Karlitskaya (desrt) 2010-04-20 21:28:31 UTC 
I committed a changed-around patch that's a bit less redundant.  Thanks for the report!