> When OurApp.exe starts up, it invokes Tcl/Tk's "wish" shell, and passes > OurScript.tcl to it for interpretation. (The actual Tcl/Tk installation on my > machine is ActiveTcl 8.4., but that's not really important.)
Well that depends. How does your application access the file "OurScript.tcl"? What I mean is what path do you use? Is it a Cygwin (posix) path or a Win32 path? What I'm thinking is that you are giving a windows version of wish a posix path, which it will not be able to understand. > Now, when I double-click on OurApp.exe in Windows Explorer, I get the > following error message from wish: > > Error in startup script > couldn't read file "/cygdrive/c/OurAppFolder/OurScript.tcl": no such file > or directory > > But when I open a DOS prompt in OurAppFolder and start OurApp from > there, then everything's fine. (Notice that it's a plain DOS prompt, not > Cygwin's bash.) > > So my question is: what's the reason for this behavior? To me it seems > that the C:\OurAppFolder\OurScript.tcl path gets transformed into its > Cygwin equivalent, and wish doesn't understand the transformed path. > But why is everything OK from the DOS prompt? And is there a way to > make the double-click work as expected? Because wish is a part of the ActiveTCL distribution, and thus a Win32 executable, that won't know what a Cygwin path is or where it points to. Regards, Elfyn McBratney [EMAIL PROTECTED] www.exposure.org.uk -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
