![](https://secure.gravatar.com/avatar/1fa3408864fb9341c38d2e55bd4d8fdd.jpg?s=120&d=mm&r=g)
Ted Gould wrote:
On Fri, 2005-11-18 at 10:30 -0600, aaron@...749... wrote:
Last night I added a short blurb to http://wiki.inkscape.org/cgi-bin/wiki.pl?GettingExtensionsWorking about how I was able to make pdf output work on WinXP with ghostscript.
I've been thinking about what if any of that should go into cvs and how would we ever make an inx file cross platform in a situation like this. But it just occured to me that for in/output extensions this isn't necessary. An inx for each platform could coexist as long as they have appropriate dependency tests. Because they don't show up when the deps aren't met. So I guess I just need a proper test for windows.
Perhaps we should make an operator in the .inx files to check the platform. Then we could guarantee that the .inx file is only used on the one that is supported. Would that work?
Oh, that might help but I wasn't realy thinking about such a thing. The problem is how to test for or even find the executable on windows. Ghostscript is unlikely to be in the path. The default install location is %programfiles%\gs\gs8.51 which expands to c:"Program Files"\gs\gs8.51\ here on my laptop, but it could just as easily be on e:. Looking at the path you will notice another problem. The version is part of the path. At work I have gs 8.53, so a single test won't find both. I was hoping someone with more knowledge of windows could comment. No offense, Ted. But you don't know windows. And I use windows but it has always seemed like black magic to me.
Aaron Spike