Aaron and Sarah Spike wrote:
bulia byak wrote: There is also a problem of crafting inx files in such a way that they convey the proper information for an extension to run on any platform withouth platform specific inx files. One such problem is the interpreter (for extensions that require one). How can python be found if it is called by python on linux and python.exe on windows? Other dependencies have the same problem.
This could be less of a problem than it might seem. If the path includes the Python directory (which I believe the installer on win32 does, but someone should check that), then just running: python script.py Would in fact run the script on Windows (and I presume on Linux too). Another way would be to use ShellExecute on Windows (and execute the script directly) and hope file associations have been set up to open the scripts with the right interpreter (this is definitely done by the Python installer on Windows). ShellExecute might have some other problems though (I don't know whether or not input/output redirection would work for example), but those could probably be worked around if necessary.
There is also something called Windows Script Host, for which at least ActiveState apparently provides scripting engines for Perl and Python (and MS of course provides support for JScript and VBScript by default). But I never used this myself, so I have no idea how how easy this would be to use (but as far as I can tell there's a good chance this wouldn't be harder than simply running the script directly or some program with the script as a parameter). This would be VERY platform-specific though, and probably not necessary.
I'm less familiar with other scripting languages, so I can't comment on them, but presumably the above techniques would also work for them (as long as their installer sets the path and/or file associations).