perfect:
...
<DataVersion>1612</DataVersion>
...
Now I'm a real happy user... ;-)
I will make sure it will be tested with more, different and bigger maps.
But all will be built via the same building environment, therefore, to
be honest, I do not expect any additional problems just due to other maps.
I did most of the tests until now on windows, I will also do some linux
testing of this branch.
Thanks for the quick fix of this...
Cheers
Patrik
On 15.12.2016 21:57, Steve Ratcliffe wrote:
Hi Patrik
I'm just wondering about DataVersion being 100 eventhough I call mkgmap
with --product-version="1612". Shouldn't that version go into that
DataVersion also ? A gmap archive structure created with jmc_cli does
fill DataVersion with the 'correct' number, btw.
Yes you are correct. I have added support for --product-version.
This means that it should really be called --family-version using our
as you can't specify one for each product.
..Steve
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
