On May 03, 2005, at 00:33, David Steuber wrote:
The way I've organized files in CVS may be a little weird. I wanted to keep CL-Carbon separate from anything that may use it like Example. Here is a simple step by step 'script' that should allow you to build a working application bundle from the CVS sources provided you have OpenMCL properly installed with the interfaced databases. I'm assuming ~/usr/src/ which is where I like to keep my projects.
cd ~/usr/src cvs -d :pserver:anonymous@common-lisp.net:/project/cl-carbon/ cvsroot login cvs -z3 -d :pserver:anonymous@common-lisp.net:/project/cl-carbon/ cvsroot co Example cd Example/lib cvs -z3 -d :pserver:anonymous@common-lisp.net:/project/cl-carbon/ cvsroot co CL-Carbon cd .. ln -s lib/CL-Carbon/cl-carbon.asd cl-carbon.asd sh make.sh
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.
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.
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. --jon