Hello,

It's been a while, but if I remember well, there was a problem with
the Document based applications. I was unable to make them work with
macpack. That's why I decided to rewrite the launch script (you will
notice that when the script creates the symlink to mono binary, it
does it in a different location, so Document based applications work).

Regards, Laurent Etiemble.

2008/11/16 marc hoffman <[EMAIL PROTECTED]>:
> Laurent,
>
>> Monobjc is very strict when it comes to NIB loading, so I suspect a
>> path problem at the startup.
>>
>> As the only major difference is the packaging, can you try to use the
>> NAnt tasks to do the packaging ?
>>
>> You can use the NAnt script use in the sample app as a starting point.
>> You MUST run the nant command under MacOS X, as during the packaging,
>> a chmod command is launched to give the startup script the executable
>> flags.
>
> found the problem - apparently monobjc needs an entirely different launcher
> SH script. i extracyed that from NAnt.Monobjc.dll and added it to our
> MacPack as option, and now it's working fine!
>
> any specific reason you chose to not just work with the "standard" launch
> script ghat Mono's MacPack uses?
>
> yours,
> marc
>

Reply via email to