On Fri, 2007-06-29 at 15:22 -0700, Ted Gould wrote:
How would said full path be determined?
That is exactly what I want to know.
If we can keep it relative to the parent directory, that would be optimal.
Then we will need to make that the working directory for shelling out to python.
Would "INKSCAPE_EXTENSIONDIR" work in this case?
Is it dynamic on win32? For instance, does it work with multiple installs?
Hmm, it looks like this is not really used in win32. In Linux this is configured by autotools to be the DATADIR plus an offset. But, it is also used by the autopackaging stuff -- where it is generated automatically. But, win32 moves all that stuff out.
I think the real solution here is to fix INKSCAPE_DATADIR and INKSCAPE_LIBDIR on win32 so that they are meaningful. That would help with other paths also.
--Ted