On 2012-01-13 16:10, Steve Ratcliffe wrote:
On 13/01/12 19:05, Richard Hansen wrote:
Hi all,
I have stumbled across a couple of mkgmap command-line argument parsing
bugs:
1. (all?) command-line arguments after '-c template.args' are ignored
The order of options intentionally matters. Option
On Fri, Jan 13, 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
>
On 14 Jan 2012, at 03:03, Richard Hansen 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.
>>>
>>>
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 i
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 t
On 2012-01-13 16:10, Steve Ratcliffe wrote:
> On 13/01/12 19:05, Richard Hansen wrote:
>> 1. (all?) command-line arguments after '-c template.args' are ignored
>
> The order of options intentionally matters. Options only affect files
> that follow them on the command line (or within a command file
On 13/01/12 19:05, Richard Hansen wrote:
> Hi all,
>
> I have stumbled across a couple of mkgmap command-line argument parsing
> bugs:
>
> 1. (all?) command-line arguments after '-c template.args' are ignored
The order of options intentionally matters. Options only affect files
that follow them o
Hi all,
I have stumbled across a couple of mkgmap command-line argument parsing
bugs:
1. (all?) command-line arguments after '-c template.args' are ignored
2. '--generate-sea' produces the following error message (I have to use
'--generate-sea=multipolygon' even though multipolygon is suppose
