From: blackrain ()
Date: May 13, 2008
Subject:
Re: Building Sclang Executable on OS X (leopard or
On Mon, May 12, 2008 at 9:52 PM, scacinto
wrote:
> 2) I then have to edit the file /SCClassLibrary/Platform/osx/OSXPlatform.sc
> so it looks like the following.
>
> startup {
> Document.implementationClass.startup;
> // make server window
> //Server.internal.makeWindow;
> //Server.local.makeWindow;
> // if ( this.hasFeature( \emacs ) ) {
> // Document.implementationClass.startup;};
> this.loadStartupFiles;
> }
>
> This edit reflects the use of the "emacs" code suggested earlier in this
> thread. This caused an error however, so I've commented it out.
>
No. The reason of the errors you still get is that you keep working on
a modified version of the document and 'svn update' will not restore
files that you have touched (say edited).
This is why the steps in 'README SCLang OSX' state clearly that you
should /export/ a fresh copy of SCClassLibrary and _then_ make the
editions on that copy.
The contents of OSXPlatform:startup (as noted on the instructions
file) should be the following:
startup {
// Document.implementationClass.startup;
if ( this.hasFeature( \emacs ) ) {
Document.implementationClass.startup;
};
// make server window
// Server.internal.makeWindow;
// Server.local.makeWindow;
this.loadStartupFiles;
}
As I stated previously on this thread, these modifications will allow
scel Document implementation to take in if the package is installed
and do nothing if its not.
In your version, you are calling Document.implementationClass.startup
unconditionally.
This calls Cocoa primitives and thus, the 2 block long list of
warnings bells and whistles at lib compile time.
cheers,
x
_______________________________________________
sc-users mailing list [EMAIL REMOVED] http://lists.create.ucsb.edu/mailman/listinfo/sc-users