logo separator

[mkgmap-dev] Installer not working

From Gerd Petermann GPetermann_muenchen at hotmail.com on Mon Jan 2 17:17:45 GMT 2017

Hi,

I think the problem is that mkgmap doesn't work properly when started in an environment with something like -Dfile.encoding=UTF-8.
The --nsis option will probably produce a scrambled file in that situation.
I guess we can change this in the same way as with the last patch from Mike Baggaley, but I have no idea if that would cause new trouble for others.
So, as a work around, I suggest to run mkgmap with something like -Dfile.encoding=ISO8859_15 . This should produce a *.nsi file which is not utf-8.
If makensis with /INPUTCHARSET OEM or whatever it accepts.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Patrik Brunner <patrik.brunner at gmx.net>
Gesendet: Montag, 2. Januar 2017 18:03:42
An: mkgmap-dev at lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Installer not working

Stéphane,

those effects remind me my problems earlier...

questions:
- when did this problem start ? (sorry, can't read up the complete history where I am right now).
- did/does it also happen wir releases prior to r3730 ?

r3730 was the release when the so called 'file-encoding' branch has been merged back.
This 'file-encoding' branch was handling issues with utf-8 and other codepages with regards to license files and copyright files....
The effects look very similar to what I encounterd with the old versions.... that was why some changes regarding license and copyright files has been done.

This might had some influences in other areas also.

Cheers
Patrik

Gesendet: Montag, 02. Januar 2017 um 17:31 Uhr
Von: "Stéphane MARTIN" <st3ph.martin at laposte.net>
An: "Development list for mkgmap" <mkgmap-dev at lists.mkgmap.org.uk>
Betreff: Re: [mkgmap-dev] Installer not working
Hi,

$ makensis -INPUTCHARSET UTF8 -V3 20000000.nsi
MakeNSIS v31-Dec-2016.cvs - Copyright 1999-2016 Contributors
See the file COPYING for license details.
Credits can be found in the Users Manual.

Processing script file: "20000000.nsi" (UTF8)

Processed 1 file, writing output (x86-ansi):

Output: "/home/steph/osm/work_Mayotte/Mayotte OSM default.exe"
Install: 5 pages (320 bytes), 1 section (4120 bytes), 431 instructions
(12068 bytes), 442 strings (14178 bytes), 5 language tables (1610 bytes).
Uninstall: 1 page (128 bytes), 1 section (4120 bytes), 56 instructions
(1568 bytes), 204 strings (4884 bytes), 5 language tables (990 bytes).
Datablock optimizer saved 32134 bytes (~0.6%).

Using lzma (compress whole) compression.

EXE header size: 49152 / 36352 bytes
Install code: (29664 bytes)
Install data: (4767409 bytes)
Uninstall code+data: (28546 bytes)
Compressed data: 880245 / 4825619 bytes
CRC (0x72A88098): 4 / 4 bytes

Total size: 929401 / 4861975 bytes (19.1%)

Same result.

First I do not understand why mkgmap produces a .nsi in UTF-8 with "d�j�
install�" even if this is not the source of the problem for BaseCamp.

Steph

Le 02/01/2017 à 06:53, Gerd Petermann a écrit :

Hi Steph,

did you try the INPUTCHARSET option of makensis ? Maybe version 3
requires that.

Gerd
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


More information about the mkgmap-dev mailing list