On 21/3/10 00:10, Wolf Drechsel wrote:
On 20/3/10 13:02, ~suv wrote:
On 20/3/10 12:36, Michael Wybrow wrote:
On 20/03/2010, at 1:20 AM, Stuart Edwards wrote:
- My opt/local/etc/pango contains only pango.modules and pangorc.
There is a pangox.aliases in the original download file for pango 1.26 but the local portfile process did not include its installation in opt/---
Strange. I'm using pango 1.24.5 on my build machine, and a "port contents pango" show that file as being installed by pango. Don't know why this shouldn't be the case for you too.
AFAIK 'pango +no_x11 +quartz' doesn't install files related to the X font backend.
On my aqua build there is no pangox.aliases - it's only here:
/Applications/Inkscape.app/Contents/Resources/etc/pango/pangox.aliases
but this is a X11 build, not an aqua one.
I'm quite sure you dont need pangox.aliases in an aqua build - mine doesnt have it, and it works quite nicely.
Sorry for insisting in that: There is really no output, neither in console.log, nor in crash reporter??? - That's the really interesting thing to me!
I don't understand what you are referring to - output from what?
How can we launch a packaged inkscape from the command line? - I tried a
Inkscape-r9213.app/Contents/Resources/bin bub$ ./inkscape
…that launched, but most of the icons were substituted by a red cross, which is not the case normally. Hopefully, a better method of launching it from the command line will give us some hints.
Please see bug #181639 and bug #435812 for details. To launch the packaged application from the command line:
1) don't 'cd' into the package 2) use the full path name to the launcher or to the shell wrapper script:
$ /Applications/Inkscape.app/Contents/MacOS/Inkscape
or
$ /Applications/Inkscape.app/Contents/Resources/script
3) to open a file from the command line, use its full path name, even if it is in the current directory.
hth, ~suv