Hi, On Wed, 10 Dec 2008 08:35:13 +0900, Eric Y. Kow <[EMAIL PROTECTED]> wrote: > Earlier, I might have reported that running wxhakell apps on MacOS X > doesn't work from the command line anymore (except by opening the > app bundle). > > I just wanted to throw in a slight twist: if you run macosx-app foo, > you can then invoke foo.app/Contents/MacOS/foo in order to run your > GUI program from the command line
I think macosx-app causes your problem. I can run foo and foo.app/ on my Intel Mac environment, too. shelarcy$ open GLMultiCanvas shelarcy$ /Users/shelarcy/.cabal/lib/wxhaskell-0.11.0/bin/macosx-app shelarcy$ open GLMultiCanvas.app/ shelarcy$ open GLMultiCanvas.app/Contents/MacOS/GLMultiCanvas But when I run macosx-app, I can't run foo anymore. shelarcy$ open GLMultiCanvas LSOpenFromURLSpec() failed with error -10828 for the file /Users/shelarcy/Desktop/wxhaskell/samples/contrib/GLMultiCanvas. I think reasons of this behavior is that macosx-app made classic application (foo) and application bundle (foo.app) from foo executable file. So, when we run macosx-app, we can't run foo without classic environment. Best Regards, -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
