[mkgmap-dev] mkgmap -c problem (relative paths)

Thu Mar 7 10:22:27 GMT 2019

Hi all,

attached is a patch for the documentation. It adds the text
        Note that relative paths given in the file are assumed to be relative to the
        location of the file.
here:
-c filename
--read-config=filename
        Each line of the named file contains a command option in the form
        option=value or option:value.  The options are included as arguments of
        the executed command as if they had been specified on the command line.
        Note that relative paths given in the file are assumed to be relative to the
        location of the file.
        Lines beginning with a # character are ignored and can be used as
        comments.  Any command line option can be specified, however the
        leading '--' must be omitted.  The short option names with a single
        '-' cannot be used, simply use the long name instead.

I hope this is not too confusing?
I nobody suggest an inprovement I'll commit it on sunday.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Ranko Jaksic <ranko.jaksic at zgi.hr>
Gesendet: Mittwoch, 6. März 2019 22:22
An: mkgmap-dev
Betreff: [mkgmap-dev] mkgmap -c problem (relative paths)

Hello,

I use config files with mkgmap and define input-files using relative paths.
Example from my config file "osm-options":

mapname: 80100003
input-file: data/80100003.osm.pbf

This works well when the config file is in the same directory where mkgmap is started.
When invoked with "-c osm-options" mkgmap finds my input file just fine.

To tidy up my environment I moved all my config files into a config subdirectory.
Now when I invoke mkgmap with "-c config/osm-options" I get the following error:

SEVERE (Main): .\config\data\80100003.osm.pbf: file .\config\data\80100003.osm.pbf doesn't exist

It appears that mkgmap interprets my relative paths relative to the config file location,
and not (as I expected) the mkgmap cwd!

This seems to be a bug since the description for -c states:
"The options are included as arguments of the executed command as if they had been specified on the command line."

I tested using the latest r4282 on Windows.

Regards,
Ranko

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: relative_path.patch
Type: application/octet-stream
Size: 1445 bytes
Desc: relative_path.patch
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20190307/72206f8a/attachment.obj>