Inkscape Shell output path
Bug #1418650 reported by
amafernandes
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
Inkscape version: 0.91 r13725
Platform: OSX 10.9.5 64 bits
Description:
Using Inkscape shell in interactive mode, when using relative output paths, the file is saved inside the application Bundle. This worked properly in version 0.48.
| tags: |
added: cli osx packaging removed: interactive mac shell |
Revision history for this message
| su_v (suv-lp) wrote | #1 |
To post a comment you must log in.
See
https:/
and also
https:/
It didn't really work with 0.48 either, you just happened to not rely on any file of the installed shared Inkscape resources. Due to changes unrelated to osx packaging, it is now (with 0.91) required to make sure that the current working directory is changed to the bundle top in the innermost launcher shell script (as detailed in the comments of the script).
Running '/Applications/
If you need to run Inkscape via command line, I would recommend to install it as such (e.g. via MacPorts) - the current bundle structure has known limitations (it is based on legacy code to implement sort-of relocation support for osxapp-configure builds), and with 0.91 does require to always use absolute paths to files referenced on the command line (otherwise a necessary resource (units.xml) can't be loaded and this will affect e.g. export to bitmap as soon as a dimension or resolution is specified on the command line).
Linking as duplicate to bug #181639.