Hi,
On Wed, 10 Dec 2008 08:35:13 +0900, Eric Y. Kow <eri...@gm...> 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/
|