Hi Have noticed that mkgmap creates a temporary typ file by placing an x in front of the filename - ie original mytyp.typ becomes xmytyp.typ (if I write protect the TYP file directory it spits out:Could not write temporary TYP file: K:\dum\xmytyp.typ) this is not a problem itself but in the NSIS script it still refers to the temporary file. in the .nsi script I get : File "xmytyp.typ" and not : File "mytyp.typ" Any ideas? r Nick I use java -Xmx1024m -ea -jar C:\A_UPL2~1\MKGMAP~1\MK90EB~1\mkgmap.jar --mapname=78200494 --family-id=6228 K:\dum\mytyp.typ --nsis c:\map.osm -- View this message in context: http://gis.19327.n5.nabble.com/nsis-typ-file-name-tp5826319.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi
Have noticed that mkgmap creates a temporary typ file by placing an x in front of the filename -
ie original mytyp.typ becomes xmytyp.typ
The xmytyp.typ file is rewritten with the correct family and product id. That is the file that needs to be written into the gmapsupp or used for mapsource or basecamp. Of course if mytyp.typ already has correct family and product id's then you could use that too, but mkgmap does not attempt to figure that out. I mostly expect people to start with a .txt file where the ID's get set correctly as part of compiling it in the first place. ..Steve
(if I write protect the TYP file directory it spits out:Could not write temporary TYP file: K:\dum\xmytyp.typ)
this is not a problem itself but in the NSIS script it still refers to the temporary file.
in the .nsi script I get :
File "xmytyp.typ" and not : File "mytyp.typ"
Hi Steve I understand what you are saying and it makes sense to get mkgmap to match the FID and PID Does that explain why the x---.typ doesn't get deleted. The only interesting point is that as far as I can tell in the output dir I don't see the x---.typ As I said it's not a big issue. r Nick -- View this message in context: http://gis.19327.n5.nabble.com/nsis-typ-file-name-tp5826319p5826328.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
On 05/12/14 10:09, nwillink wrote:
Does that explain why the x---.typ doesn't get deleted.
Yes it is still needed to create the windows installer. Its not really a temporary file.
The only interesting point is that as far as I can tell in the output dir I don't see the x---.typ I'm concerned that you say that if you disallow writes to the directory the file is not created but is still referred to in the nsis file. The code seems like it should stop with an error if it is unable to create or write to the x--.typ file. If that is not happening it would be a bug. I'm unable to reproduce that with a quick test.
..Steve
You are right, the nsis code stops with nan error. The fact that mkgmap stops is I think more to do with W7 and its security settings. I'had denied all read & write privileges to work out where the xtyp came from. r Nick -- View this message in context: http://gis.19327.n5.nabble.com/nsis-typ-file-name-tp5826319p5826333.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
participants (2)
-
nwillink -
Steve Ratcliffe