
I wish to make a mapsource installer for the Baltic map. Can anyone please provide a simple recipe for doing that? Thanks, Mark

On 02/01/10 14:33, Mark Burton wrote:
I wish to make a mapsource installer for the Baltic map.
Can anyone please provide a simple recipe for doing that?
1. Obtain the makensis program. Either the windows version at http://nsis.sourceforge.net/Main_Page (works under wine on Linux) or the Linux version from your distribution. On Fedora you just type its name and the right package is installed which happens to be mingw32-nsis. 2. Run mkgmap with the --nsis option. This will give you a .nsi file (by default osmmap.nsi). This is just a text file that you can adjust if need be. 3. Run makensis osmmap.nsi this should create a windows installer for mapsource. Check that it works on Vista/Windows7 as I'm not sure if .nsi file has the line to request installation privs. ..Steve

Hi Steve, Thanks for the quick response.
2. Run mkgmap with the --nsis option. This will give you a .nsi file (by default osmmap.nsi). This is just a text file that you can adjust if need be.
OK - I notice that it misses out the TYP file and indexing files. It would be good if it included them (please could you add them into the script).
3. Run makensis osmmap.nsi this should create a windows installer for mapsource.
Unfortunately, this doesn't work on my Ubuntu system as it's missing some part of makensis. So I installed the windows version and that runs OK and produces an installer.
Check that it works on Vista/Windows7 as I'm not sure if .nsi file has the line to request installation privs.
Someone will have to do that for me as I don't have access to those systems. Cheers, Mark

2. Run mkgmap with the --nsis option. This will give you a .nsi file (by default osmmap.nsi). This is just a text file that you can adjust if need be.
OK - I notice that it misses out the TYP file and indexing files. It would be good if it included them (please could you add them into the script).
Mark, I am not familiar with TYP files, but if you provide me a sample with all the files you submit to mkgmap, the command line and which files should be included in the install I will be glad to improve the NSIS file generation. Thanks, N.

Hi Nakor,
Mark, I am not familiar with TYP files, but if you provide me a sample with all the files you submit to mkgmap, the command line and which files should be included in the install I will be glad to improve the NSIS file generation.
If you give the --index option mkgmap generates osmmap.mdx and osmmap_mdr.idx files that should be installed with the others and have registry entries like these: "SOFTWARE\Garmin\MapSource\Families\${REG_KEY}" "IDX" "$INSTDIR\${MAPNAME}.mdx" "SOFTWARE\Garmin\MapSource\Families\${REG_KEY}" "MDR" "$INSTDIR\${MAPNAME)_mdr.img" If a TYP file is given as one filenames to mkgmap, you could include it in the list of files to install and generate a registry entry for it: "SOFTWARE\Garmin\MapSource\Families\${REG_KEY}" "TYP" "$INSTDIR\TYPEFILENAME" Is that enough info? Cheers, Mark

Hi Mark
OK - I notice that it misses out the TYP file and indexing files. It would be good if it included them (please could you add them into the script).
It will include the index files if --index is given. Of course this also generates the index too and it might be good to be able to build from a previously generated set of files. I've created a patch (attached) that picks up mdr and typ files and adds them if present. It could do with with a tad more testing than I've given it. ..Steve

Hi Steve,
It will include the index files if --index is given. Of course this also generates the index too and it might be good to be able to build from a previously generated set of files.
Hmm, I'm specifying --index but it's not putting anything into osmmap.nsi that's related to MDR or IDX files. Something's not right.
I've created a patch (attached) that picks up mdr and typ files and adds them if present. It could do with with a tad more testing than I've given it.
Thanks, I will give it a go. Cheers, Mark

Steve,
Thanks, I will give it a go.
No sooner said than done. 2 issues observed in osmmap.nsi: 1 - the WriteRegStr line for the TYP file includes the TYP file's path when it should be stripped? i.e. WriteRegStr HKLM "SOFTWARE\Garmin\MapSource\Families\${REG_KEY}" "TYP" "$INSTDIR\/home/markb/OSM/M000038d.TYP" 2 - the delete registry entry for the TYP file is the same as the create entry! WriteRegStr HKLM "SOFTWARE\Garmin\MapSource\Families\${REG_KEY}" "TYP" "$INSTDIR\/home/markb/OSM/M000038d.TYP" You're right, the IDX/MDR stuff does get generated, I had inadvertently removed the --index option and was just seeing old index files in my maps. Cheers, Mark

On 02/01/10 23:23, Mark Burton wrote:
Steve,
Thanks, I will give it a go. 1 - the WriteRegStr line for the TYP file includes the TYP file's path when it should be stripped? i.e.
Would giving an arbitary Unix path even work in a windows installer? I always have all files in the current directory when making an one. New patch attached. ..Steve

Steve,
Thanks, I will give it a go. 1 - the WriteRegStr line for the TYP file includes the TYP file's path when it should be stripped? i.e.
Would giving an arbitary Unix path even work in a windows installer?
Well, the problem would be the same if you were running it under windows. It's not just a unix thing.
I always have all files in the current directory when making an one.
That's one solution - I'll just edit the generated .nsi file and fixup the line, it's no big deal.
New patch attached.
Thanks, giving it a go... looks good. Cheers, Mark

On 01/02/2010 03:33 PM, Mark Burton wrote:
I wish to make a mapsource installer for the Baltic map.
Can anyone please provide a simple recipe for doing that?
I made one for my topo map based on the NSIS script discussed on the list a few weeks ago. You can find it here: http://www.kleineisel.de/blogs/index.php/osmmap/2009/11/18/title-3 The NSIS config file used to generate the exe is here: http://www.kleineisel.de/blogs/media/blogs/osmmap/0911/OSM_SRTM_Germany.nsi I decided to make an installer that installs the gmapsupp.img instead of having an installer exe which contains all the data. This way there is only one big download file and the installer is very small. It uses the gmt.exe from the wgmaptool package for splitting the gmapsupp.
participants (4)
-
Mark Burton
-
Nakor
-
Ralf Kleineisel
-
Steve Ratcliffe