[Ecls-list] Re: CVS run-in-place ?

[GP lisper]

On Mon, 8 Aug 2005 01:09:41 +0200, <der_julian at web.de> wrote:
> On Mon, 08 Aug 2005 00:35:09 +0200
> Maciek Pasternacki <maciekp at japhy.fnord.org> wrote:
>
>> On Prickle-Prickle, Confusion 73, 3171 YOLD, GP lisper wrote:
>> 
>> > Is there a simple way to 'test run' a newly built CVS copy?  One
>> > that avoids the 'make install' step?  I know that you can do this
>> > with one of the popular GNU programs, probably emacs.
>> >
>> > This is for an automated CVS update script, one that ensures that
>> > ECL will run the desired code prior to replacing the system ecl
>> > installation.
>> 
>> In UNIX environment, LD_LIBRARY_PATH=. ./ecl in ecls/build/ should do
>> (check with ldd if ld.so will find correct libecl.so instead of
>> system-wide-installed one).  If you want to also load new fasl files
>> (cmp.fas, sockets.fas, asdf.fas), you may need to redefine `sys:'
>> pathname translation to point to build directory.
>
> Which can be done via -dir. So this command should work in the build
> directory:
>
> env LD_LIBRARY_PATH=. ./ecl -dir .

Ah, I knew the two pieces, but didn't put them together.

Might I suggest that something along the lines of the above find it's
way into the FAQ.

Thanks to all for the replies!


-- 
So I found the holy lisp,
Pure were curves that are parens
Forms of such short text,
Bestowing beautiful simplicity