[cl-carbon-devel] Building Example and CL-Carbon from CVS

[David Steuber]

On May 3, 2005, at 10:10 AM, Jon Allen Boone wrote:
>
> On May 03, 2005, at 00:33, David Steuber wrote:
>>
>> This should result in a working Example.app in the bin directory.
>
> I'd recommend the following changes to your script:
>
> * install CL-Carbon in ~/usr/src
> * make the symbolic link to ../CL-Carbon/cl-carbon.asd
>
> This makes it clearer that the CL-Carbon module is separate from those 
> modules that make use of it.

This will certainly work.  Although I have had recompile trouble due to 
stale dfsl files not being deleted by the make.sh script like this.  It 
seems find does not follow symlinks.  Perhaps there is a switch for 
that?

>> I've not included swank in Example.  I recomend setting up another 
>> project for that.  OpenGL Demo on my personal website shows how swank 
>> is used so that you can use Emacs + Slime to connect to the running 
>> application.
>
> That seems acceptable.  I'd even recommend that we find out if there 
> is a way to get swank w/out getting all of slime.  If so, then I'd 
> suggest putting it in the same ~/usr/src directory and linking back to 
> it.
>
> Of course, these are temporary hacks to start off with.  We should 
> really use defsystem or asdf to include these lisp libraries.

I'm actually using ASDF.  There should be an example.asd for building 
the example application.  It depends on cl-carbon.asd.  Unlike SBCL, 
OpenMCL does not have any default locations for systems out of the box. 
  I've not tried to set any of that up.

>> It may be a good idea to make the build system part of CL-Carbon.  
>> That's the way Bosco handles it.
>
>   I've not used Bosco, so I'm not totally sure what you mean.

Bosco is an OS X application building tool created by Mikel Evins.  I 
used it as a spring board to figure out how to create application 
bundles using OpenMCL.  I'm not really using any Bosco code anymore, 
but the make.sh script is a vague remnant of what Bosco used.  I'm 
doing things rather differently though like setting a main function in 
the save-application call and not even providing for Cocoa.

I've just checked in some interesting changes for CL-Carbon.  I believe 
I have vastly improved the Carbon event to CLOS method dispatch mapping 
code.  If you want to get e-mail when CVS check ins happen, there is a 
cl-carbon-cvs mailing list on common-lisp.net that you can sign up for.

I'm not sure when my next set of changes will be.  Now that I've 
scratched the event handling itch (and assuming it holds up), I'm back 
into a thinking about what's next mode.