Inkscape

[OSX] can't launch inkscape from the console (Inkscape.app)

Bug #793227 reported by Paaguti-hotmail on 2011-06-05

This bug report is a duplicate of: Bug #181639: Command-line invocation on Mac OSX partially broken. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Inkscape	New	Undecided	Unassigned

Bug Description

OSX 10.6.5
Inkscape.app version 0.48.1 r9760
I need to be able to convert some .SVG files into .PDF using the command line (well, through GNU Make) in a Linux compatible manner. I'm working on my PhD with a Linux and a Mac and I'd like to be able to have a uniform editing environment.

Workaround: I have put the attached file in my PATH and I can issue commands like

inkscape -z --export-pdf=image.pdf --file=image.svg

Caveats: The first time the script is called, it will activate the X11 environment and the
call will not be very fast. From then on, the conversions are as fast as in Linux.

Related:
Bug #181639 “Command-line invocation on Mac OSX partially broken”

See original description

Tags:

Revision history for this message

Paaguti-hotmail (paaguti-hotmail) wrote on 2011-06-05:

script to launch inkscape from bash, place it in the PATH Edit (83 bytes, text/plain)

su_v (suv-lp) on 2011-06-05

tags:	added: cli packaging removed: from launch shell workaround
summary:	- [OSX] can't launch inkscape from the console + [OSX] can't launch inkscape from the console (Inkscape.app)

su_v (suv-lp) on 2011-06-05

description:

updated

Revision history for this message

su_v (suv-lp) wrote on 2012-07-09:

Drawback of the proposed solution/workaround: it won't work with file formats which depend on an script-based extension, or more complex command line usage (e.g. involving verbs executing extensions or filter effects): the script does not fully set the required shell environment, and the inkscape process launched with this command is not able e.g. to load any extension files, or predefined filter effect from the shared resources included in the application bundle.

A better solution would be to call '/Applications/Inkscape.app/Contents/Resources/script' instead, with the drawback that files provided as command line arguments then always must be referenced with their full (absolute) path names. When used within other scripts, this isn't really a problem (it might be more cumbersome though for occasional usage on the command line).

Revision history for this message

su_v (suv-lp) wrote on 2015-10-16:

The proposed solution in this report is neither recommended, nor will it work as is with Inkscape 0.91 (any files referenced on the command line will require absolute paths). Linking as duplicate to bug #181639 which tracks the known limitations of using current packaging as OS X application bundle via command line interface (mostly legacy issues due to the decision to implement relocation support for osxapp based on paths relative to the bundle's top dir). See more recent comments there wrt changes in Inkscape 0.91.