[mkgmap-dev] Mkgmap always returns exit code 0 even when it fails

Mon Jan 13 08:12:47 GMT 2014

Hi Paco,

I agree, but I found no simple way to change mkgmap.
I assume that you consider a non empty stderr file as
an error, so maybe we can check whether anything was
written to stderr, but sometimes we use this file also for
important hints like this:
"WARNING: input files have different code pages"

BTW: Also splitter doesn't make sure that it ends
with a non-zero return code in case of errors, but
it tries to do so.

Gerd

> Date: Sat, 11 Jan 2014 00:22:54 +0100
> From: paco.tyson at free.fr
> To: mkgmap-dev at lists.mkgmap.org.uk
> Subject: [mkgmap-dev] Mkgmap always returns exit code 0 even when it fails
> 
> Hi,
> 
> I'm building a map generation tool with Ant. Problem is that if mkgmap
> encounters an error, the exit code is 0, no matter what. As this is the "OK"
> exit code, Ant carries on to the rest of the workflow.
> On the contrary, splitter does return a non zero code when it fails.
> 
> Please make mkgmap return a non zero exit code for errors.
> 
> 
> Thanks,
> Paco
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20140113/fe01d62e/attachment.html>