Hi,

the translations are not build in the process: http://build.neon.kde.org/job/xenial_release_forks_gcompris_bin_amd64/4/consoleFull
There should be a: make BuildTranslations that will compile the po files and put them in ./usr/share/gcompris-qt/translations/

Johnny

I am wagering a guess that it uses binaries which, when missing, are not properly reported via cmake, which makes it impossible for integrators to know that they are missing.

(In reply to Harald Sitter from comment #2)
> I am wagering a guess that it uses binaries which, when missing, are not
> properly reported via cmake, which makes it impossible for integrators to
> know that they are missing.

Hi,

http://build.neon.kde.org/job/xenial_release_forks_gcompris_src/4/console shows that you download the src from the gcompris website. This src (http://build.neon.kde.org/job/xenial_release_forks_gcompris_src/4/console) contains the translation files.

In the build (http://build.neon.kde.org/job/xenial_release_forks_gcompris_bin_amd64/4/consoleFull), I don't see where you call the make BuildTranslations target to build the translations. Can you add this call?
To build gcompris with the translations, you need to do: cmake && make && make BuildTranslations. They are not built automatically when doing only "make".

Uhm. make all really should make translations. Not doing so is fairly non-standard by any standard really.

BuildTranslations builds translations, doesn't seeem to add them to the install target.

(In reply to Harald Sitter from comment #5)
> BuildTranslations builds translations, doesn't seeem to add them to the
> install target.

Actually it does, I am just blind.

Hi,
the main issue is fixed, I created a task to follow the adding of BuildTranslations target to make all: https://phabricator.kde.org/T4809