| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Our extractor tool was not calling setlocale(), thus it only
produced output in the C locale, ie ASCII. Oops.
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
This reverts commit 651d9e90e715ba0f4e246d03102cfb5353c19dc6.
The commit broke 'make dist' - the extract-strings sources are no
longer included in the tarball.
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
Might fix
https://bugzilla.gnome.org/show_bug.cgi?id=731602
|
|
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.
|