Non-interactive "export" doesn't work on Mac

[Masao Uebayashi]

After update to 0.91, exporting to PDF (`--export-pdf=xxx.pdf') stopped working, like:

--------8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<
% /Applications/Inkscape.app/Contents/Resources/bin/inkscape --file=rect.svg --export-eps=rect.eps

** (inkscape-bin:44419): WARNING **: Can't open file: rect.svg (doesn't exist)

** (inkscape-bin:44419): WARNING **: Can't open file: rect.svg (doesn't exist)

** (inkscape-bin:44419): WARNING **: Specified document rect.svg cannot be opened (does not exist or not a valid SVG file)
>8-------->8-------->8-------->8-------->8-------->8-------->8-------->8--------

Not only `--export-pdf'' but also any `--export-*' options don't work too.

Mac OS X 10.9.5
Inkscape 0.91

[su_v (suv-lp)]

It does work, but you need to use absolute paths to any files referenced on the command line. Note also that was never recommended nor supported to run than innermost launcher script directly on the command line (use "/Applications/Inkscape.app/MacOS/Inkscape" or "/Applications/Inkscape.app/Contents/Resources/script" instead - the requirement for absolute paths with the Inkscape 0.91 application bundle to referenced files doesn't change though).

Example:
$ /Applications/Inkscape.app/Contents/Resources/script --file="$(pwd)/rect.svg" --export-eps="$(pwd)/rect.eps"

If that is too inconvenient, I would recommend to install a regular (no bundled) build of Inkscape via MacPorts.

See also my earlier comment in
- Bug #1418650 “Inkscape Shell output path”
  https://bugs.launchpad.net/inkscape/+bug/1418650

Linking as duplicate to
- Bug #181639 “Command-line invocation on Mac OSX partially broken”
  https://bugs.launchpad.net/inkscape/+bug/181639

[su_v (suv-lp)]

Correction (fix recommendation for command line usage of Inkscape installed as OS X application bundle):
- use "/Applications/Inkscape.app/MacOS/Inkscape" or "/Applications/Inkscape.app/Contents/Resources/script" instead
+ use "/Applications/Inkscape.app/Contents/Resources/script" instead

[Masao Uebayashi (uebayasi)]

Thanks for the detailed follow-up. I can live with the absolute
work-around (I'm using a wrapper script anyway). It'd be better if
this problem could be easily found on Google.

(I have no idea what kind of pkg I was using before.)