From: Jim I. <ji...@ap...> - 2002-02-03 03:39:48
|
> > Sorry, but I didn"t get the point (maybe because I came from then UNIX side). > If I start a program in a shell in the terminal app why depends its behavior > on > the path I am on ? I linked (hard and sym) > /Applications/Wish Shell.app/Contents/MacOS/Wish Shell to /usr/bin/wish. > If I cd to /usr/bin everythings fine. If not (espically if I start scripts > using > the #!-meachnism, or by "/some/path/ > wish script.tcl" ) its broken. > > BTW: the tixwish is just a clone of your Wish Shell.ap with 3 extra lines to > load > the tix-Framework. Its the same type of Application as the Wish Shell in the > Tk-project > is. However the problem I'm talking about applies to both wish and tixwish. > And I build the wish right from your PB-project. Yes, there is something weird in how GUI apps get launched from the command line. I noticed, for instance, that if I did: cd /Volumes/Somewhere/SomeGuiApp.app/Contents/MacOS gdb ./SomeGuiApp Then the app would NOT launch (this is ANY GUI app, not just Carbon or Wish or whatever...) But if I did: gdb SomeGuiApp then it would. I haven't looked into this further yet, though. I will ask around and see if there is a good answer to this problem. > > Maybe I missed your point, but I couldn'T figure out how to get a least wish > running > in a shell in the same way I"m used to from Linux. > > Or was your point, that it doesn"t work this way on Mac OS X? > Well, it doesn't seem to, though it gets tantalizingly close sometimes. I am not sure if there is something else Wish could do at startup to make this work, or not. When I figure something out I will tell you. For now, though, I think you need to find some other way to test your Tix port... Sorry. Jim -- ++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++= Jim Ingham ji...@ap... Developer Tools - gdb |