Hi Uli,

that was probably missleading. If you don't generate your own precomp-sea data 
there is no problem at all.


If you DO generate your own precomp-sea make sure that mkgmap uses the trunk 
version of splitter.jar (or r412).

Don't copy the new splitter.jar into the lib directory of mkgmap.

I think PrecompSeaGenerator will fail early with the wrong splitter.jar.


I've mentioned this because users might simply search for splitter.jar and 
replace it with the new version from the branch.

Hope this was clearer now?


Gerd

________________________________
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von UliBaer 
<ulib...@gmail.com>
Gesendet: Dienstag, 6. Dezember 2016 16:43:09
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Splitter r483 in refactoring2 branch

Hi Gerd,

some time ago you mentioned, the new splitter branch isn't compatible with
the current mkgmap version. Are these differences not important anymore and
they can be used in combination?

Regards, Uli



--
View this message in context: 
http://gis.19327.n8.nabble.com/Splitter-r483-in-refactoring2-branch-tp5886807p5887025.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Reply via email to