[GBBopen-developer] Agenda Shell test failed on LispWorks 5.1

[Chun Tian (binghe)]

Hello Professor,

Thanks very much for these notes. Now I load initiate.lisp on LW start.

I'm trying to learn and use GBBopen in my project. For other  
questions, I'll ask in new mail threads.

Thanks again.

Regards,

Chun Tian (binghe)

>
>> I've another related question before do this test: When SVN  
>> updated, which part of the following steps still needed?
>> 1. (load "<install-dir>/startup.lisp")
>> 2. (mini-module:compile-module :gbbopen-test :propagate :create-dirs)
>> 3. (mini-module:compile-module :agenda-shell- 
>> test :propagate :create-dirs)
>
> Only #1 and #3 are needed to run the test.
>
>> 4. (load "<install-dir>/initiate.lisp")
>> 5. (compile-gbbopen)
>
> These steps (4 & 5) are only needed if you are maintaining a GBBopen  
> installation that is used by others (who don't have write permission  
> to the GBBopen directory tree).  Otherwise, you can let GBBopen  
> handle recompiling/loading the updates for you (as they are needed).
>
>> I wonder if I just run (ASDF:OOS 'ASDF:LOAD-OP :GBBOPEN) after 'svn  
>> update', can these new changes of source code be compiled?
>
> GBBopen has a minimal interface for ASDF users, so you could use it  
> to do a  compile & load on :agenda-shell-test.  However, using  
> GBBopen's Mini Module system is the preferred mechanism:
>
>  > (load "<install-dir>/initiate.lisp")
>  > :agenda-shell-test
>
> If you set up your CL environment according to the "Enhancing Your  
> Development Environment" exercise in the GBBopen Tutorial (highly  
> recommended), then you would only need to enter:
>
>  > :agenda-shell-test
>
> after starting up your LispWorks session.
>
>
>


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.