Extending metadata mkgmap default logging output
Hello, Is there a way to get the mkgmap version number in the logfile? I know it is possible to use the -version option but this means an extra execution of mkgmap. There is already a default output like this: Time started: Thu Apr 23 07:56:43 CEST 2020 Found one style in ..\..\Dropbox\Garmin\Build\Style - Jbm finished check-styles Number of MapFailedExceptions: 0 Number of ExitExceptions: 0 Time finished: Thu Apr 23 07:57:17 CEST 2020 Total time taken: 33 seconds Could the mkgmap version number be part of this metadata? Kind regards, Joris
Hi Joris, I don't remember why the version is not always printed. I see no problem to do that. OTOH: What's the problem with the additional execution of java -jar mkgmap.jar --version? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joris Bo <jorisbo@hotmail.com> Gesendet: Donnerstag, 23. April 2020 09:12 An: Development list for mkgmap Betreff: [mkgmap-dev] Extending metadata mkgmap default logging output Hello, Is there a way to get the mkgmap version number in the logfile? I know it is possible to use the –version option but this means an extra execution of mkgmap. There is already a default output like this: Time started: Thu Apr 23 07:56:43 CEST 2020 Found one style in ..\..\Dropbox\Garmin\Build\Style – Jbm finished check-styles Number of MapFailedExceptions: 0 Number of ExitExceptions: 0 Time finished: Thu Apr 23 07:57:17 CEST 2020 Total time taken: 33 seconds Could the mkgmap version number be part of this metadata? Kind regards, Joris
Hi, Thank you for the reply. It is no big deal, just handy, because I (and I guess most users) use scripts for downloading and building maps and less calls is easier to maintain the scripts. Since recently I copy the build-output-logging, template.args and used style.zip to the output installer.exe for future analysis and reference. I found myself spending a lot of time finding out why whatever feature did work half year ago and is now suddenly broken. The mkgmap version logging helps in this situations. But for now... I do an extra call to the same log.txt Kind regards, Joris -----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens Gerd Petermann Verzonden: vrijdag 24 april 2020 21:02 Aan: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] Extending metadata mkgmap default logging output Hi Joris, I don't remember why the version is not always printed. I see no problem to do that. OTOH: What's the problem with the additional execution of java -jar mkgmap.jar --version? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joris Bo <jorisbo@hotmail.com> Gesendet: Donnerstag, 23. April 2020 09:12 An: Development list for mkgmap Betreff: [mkgmap-dev] Extending metadata mkgmap default logging output Hello, Is there a way to get the mkgmap version number in the logfile? I know it is possible to use the -version option but this means an extra execution of mkgmap. There is already a default output like this: Time started: Thu Apr 23 07:56:43 CEST 2020 Found one style in ..\..\Dropbox\Garmin\Build\Style - Jbm finished check-styles Number of MapFailedExceptions: 0 Number of ExitExceptions: 0 Time finished: Thu Apr 23 07:57:17 CEST 2020 Total time taken: 33 seconds Could the mkgmap version number be part of this metadata? Kind regards, Joris _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
HI Gerd, I can't see why --version should cause termination of execution if there are other options supplied. I suggest simply changing this so that it does not cause termination. Regards, Mike -----Original Message----- From: Gerd Petermann [mailto:gpetermann_muenchen@hotmail.com] Sent: 24 April 2020 20:02 To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk> Subject: Re: [mkgmap-dev] Extending metadata mkgmap default logging output Hi Joris, I don't remember why the version is not always printed. I see no problem to do that. OTOH: What's the problem with the additional execution of java -jar mkgmap.jar --version? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joris Bo <jorisbo@hotmail.com> Gesendet: Donnerstag, 23. April 2020 09:12 An: Development list for mkgmap Betreff: [mkgmap-dev] Extending metadata mkgmap default logging output Hello, Is there a way to get the mkgmap version number in the logfile? I know it is possible to use the -version option but this means an extra execution of mkgmap. There is already a default output like this: Time started: Thu Apr 23 07:56:43 CEST 2020 Found one style in ..\..\Dropbox\Garmin\Build\Style - Jbm finished check-styles Number of MapFailedExceptions: 0 Number of ExitExceptions: 0 Time finished: Thu Apr 23 07:57:17 CEST 2020 Total time taken: 33 seconds Could the mkgmap version number be part of this metadata? Kind regards, Joris
participants (3)
-
Gerd Petermann -
Joris Bo -
Mike Baggaley