aboutsummaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorHiroshi Miura <miurahr@linux.com>2018-01-30 09:49:05 +0900
committerAlexander Karatarakis <alex@karatarakis.com>2018-01-29 16:49:05 -0800
commitd728defa671ce24abaf0e9f965cc6278c9323652 (patch)
treec79a812faf6b3c686ed9dd5907f230e992e43d70 /scripts
parente95159b5a60be3dc8ba29d7baf20ce76b47c2f0e (diff)
downloadvcpkg-d728defa671ce24abaf0e9f965cc6278c9323652.tar.gz
vcpkg-d728defa671ce24abaf0e9f965cc6278c9323652.zip
[libspatialite] fix compile error on non-latin env (#2659)
It has literals with latin chars in a C source. Unfortunately VC++ recognize source file without BOM as in OEM code not in UTF-8. It cause a strange behavior of VC++ compiler, and fails with "epsg_inlined_prussian.c(685): error C2001: newline in constant." It happens on non-latin Windows such as Japanese(CP932). It also work when changing Windows configuration "system locale for non-unicode applications" to latin one such as English(US)(CP432), but it affects all applications and users in Windows system. Signed-off-by: Hiroshi Miura <miurahr@linux.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions