[mkgmap-dev] mkgmap command-line argument parsing bugsFrom Charlie Ferrero charlie at cferrero.net on Sat Jan 14 04:55:04 GMT 2012
On 14 Jan 2012, at 03:03, Richard Hansen <rhansen at bbn.com> wrote: > On 2012-01-13 17:48, Roger Calvert wrote: >>>> The order of options intentionally matters. Options only affect files >>>> that follow them on the command line (or within a command file). So I >>>> don't think that there is a bug there. >>> >>> Ah, that's good to know. So the bug is that this behavior is not >>> documented in '--help=options'. :) >> >> Does that mean that it does not 'return' after reading a -c, so that >> only one -c can be used? > > If I understand Steve correctly, multiple -c arguments should work. > I've never tried it so I don't have any first-hand experience. > > -Richard According to a recent post on the OSM forum, multiple -c do work and thus offer a convenient way of calling both a relatively unchanging options file and a potentially frequently changing file list in the template.args.
- Previous message: [mkgmap-dev] mkgmap command-line argument parsing bugs
- Next message: [mkgmap-dev] mkgmap command-line argument parsing bugs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list