From: Keith M. <kei...@us...> - 2007-10-03 17:31:55
|
On Wed, 2007-10-03 at 07:36 -0400, Earnie Boyd wrote: > > Quoting Brian Elmegaard <be...@me...>: > > > Keith MARSHALL > > <kei...@to...> writes: > > > >> Strange. In an MSYS session, I did this: > > > > Thanks. From msys I can make it work too, but not from a windows > > command prompt. > > > > My guess would be that insight contains some MSYS POSIXY paths due to > the way it was built. Environment variables may help but I don't know > what those would be. Possibly, but I don't think so. From a raw cmd.exe shell, in a bare native console, I did: D:\> path %PATH%;D:\usr\msys-1.0.11\home\keith\kits\insight-mingw\bin D:\> insight d:\usr\msys-1.0.11\home\keith\foo.exe and I found myself debugging the same `foo.exe' as I had in the MSYS session; nothing apparently unusual -- it just worked. I did have MSYS active in another console, if that makes a difference, but the MSYS bin directory was not in the PATH for this cmd.exe shell. Regards, Keith. |