Skip to content

Commit

Permalink
Update docs about compile_mo.sh on Windows
Browse files Browse the repository at this point in the history
This is now required for the unit tests, whereas the libintl bug is no
longer relevant since we have rolled our own solution.
  • Loading branch information
jbytheway committed Sep 20, 2021
1 parent bb3e44d commit 1d6cd8d
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion doc/COMPILING/COMPILING-VS-VCPKG.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ This will configure Visual Studio to compile the release version, with support f

5. If you need localization support, execute the bash script `lang/compile_mo.sh` inside Git Bash GUI just like on a UNIX-like system. This will compile the language files that were not automatically compiled in step 2 above.

Even if you do not need languages other than English, you may still want to execute `lang/compile_mo.sh en` or `lang/compile_mo.sh all` to compile the language file for English, in order to work-around a [libintl bug](https://savannah.gnu.org/bugs/index.php?58006) that is causing significant slow-down on Windows targets if a language file is not found.
Even if you do not need languages other than English, you may still want to execute `lang/compile_mo.sh` to compile the language files if you're planning to run the unit tests, since those rely on the language files existing.

### Debugging

Expand Down

0 comments on commit 1d6cd8d

Please sign in to comment.