summaryrefslogtreecommitdiff
path: root/util
Commit message (Collapse)AuthorAgeFilesLines
* Make non-ASCII strings in ui files workMatthias Clasen2014-10-021-0/+3
| | | | | Our extractor tool was not calling setlocale(), thus it only produced output in the C locale, ie ASCII. Oops.
* util/extract-strings: Use autotools syntax for buildingRico Tzschichholz2014-08-151-8/+4
| | | | | | | Always refer to it as "extract-strings$(EXEEXT)" where needed to take cross-compilation into account. https://bugzilla.gnome.org/show_bug.cgi?id=731013
* Revert "Bug 731013 - cross-compilation broken when building extract-strings"Rico Tzschichholz2014-08-151-3/+3
| | | | | | | This reverts commit 651d9e90e715ba0f4e246d03102cfb5353c19dc6. The commit broke 'make dist' - the extract-strings sources are no longer included in the tarball.
* Bug 731013 - cross-compilation broken when building extract-stringsJehan2014-08-131-3/+3
| | | | | | It is actually a bad idea to use noinst_PROGRAMS for build tools, because it adds a $(EXEEXT). It is best to override the all target with all-local to trigger the tool build.
* util: Add missing git.mk includeJasper St. Pierre2014-06-161-0/+2
|
* Add some EXEEXT decorations backMatthias Clasen2014-06-131-1/+1
| | | | | Might fix https://bugzilla.gnome.org/show_bug.cgi?id=731602
* Move extract-strings to its own directory3.13.2Matthias Clasen2014-05-272-0/+187
This will hopefully help resolve the circular dependency between libgtk linking against inspector/libgtkinspector and inspector/ needing extract-strings from gtk/. I didn't preserve the EXEEXT decorations in this operation - automake gave me stern warnings about it, so I just dropped them all. Somebody who cross-builds GTK+ will have to reconstruct this.