[mkgmap-dev] How to solve/debug weird problem
From WanMil wmgcnfg at web.de on Fri Jan 14 21:23:30 GMT 2011
> WanMil<wmgcnfg at web.de> wrote: > >>> Index: uk/me/parabola/mkgmap/osmstyle/StyledConverter.java >>> =================================================================== >>> --- src/uk/me/parabola/mkgmap/osmstyle/StyledConverter.java (revision 1580) >>> +++ src/uk/me/parabola/mkgmap/osmstyle/StyledConverter.java (working copy) >> >> Johannes, >> >> your patch patches revision 1580. The current revision of mkgmap is >> 1773. The patched files contain lots of changes between 1580 and 1773. I >> wonder how it is possible to use your patch with the latest revision >> 1773 without manual changes? >> >> I assume either you don't use the latest mkgmap release or you haven't >> posted your latest patch. > > > I'm quite shure, both are the latest, but when I can archive the same > results without the patch (as Thorsten suggested), I'll throw it away. Your patch tells you the revision for which the patch is created: > --- src/uk/me/parabola/mkgmap/osmstyle/StyledConverter.java (revision 1580) You can see it's revision 1580 and not 1773. > > But if I need to rewrite it, any suggestions where I should start looking, to understand how > everything works together? If you are lucky you don't have to change very much. If you use eclipse or a similar development tool you can manually apply the patch to the latest release. You will get some conflicts where the patch tool cannot automatically patch and you have to resolve these conflicts. WanMil > > regards > > Johannes >
- Previous message: [mkgmap-dev] How to solve/debug weird problem
- Next message: [mkgmap-dev] How to solve/debug weird problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list