31 May
2006
31 May
'06
10:42 p.m.
Bob Jamison wrote:
- Use the one specified in the prefs, (defaults to none)....
- Use the location of inkscape.exe to hardcode the interpreter's
executable relative to it. If it doesn't exist..... 3) Search the PATH (what is currently happening).
This will still allow the end user to specify which python.exe he wants, especially if he is designing a new Effect.
I committed code to test in this order. Interpreters we package with Inkscape should be called python/python.exe, perl/perl.exe, ruby/ruby.exe, etc.
This seems to work ok on Win32. Can people please test this on Linux, to make sure that I didn't break anything? I rewrote some code away from gchar* to Glib::ustring, to better handle Unicode.
bob