[Larceny-users] Larceny-x86-iasn on Win32 & FFI

[Felix Klock]

On Feb 3, 2007, at 5:09 AM, Sven.Hartrumpf at FernUni-Hagen.de wrote:

> Fri, 02 Feb 2007 12:33:48 +0100 (CET), Sven.Hartrumpf wrote:
>
>> I just followed doc/HOWTO-BUILD for the current svn version
>> and it worked perfectly.
>
> One question remains: if "svn update" leads to some file updates,
> how should one rebuild?

Most of the time, you should be able to just redo each of the steps  
in doc/HOWTO-BUILD.  The build system is set up to avoid rebuilding  
things unless it is necessary; for example, the (build-heap)  
procedure will reuse the intermediate .lap and .lop files generated  
during a previous build for the current build, rebuilding only  
the .lap and .lop files for the .sch files that actually changed.

In a few rare situations, you will actually need to clean out the  
intermediate build products, because the stale files that are lying  
around will confuse the system.  For example, if there is a  
fundamental change to the calling conventions used for procedure  
invocation, then you would probably need to delete the .lap, .lop  
and .fasl files that are lying around.  (In principle, this should  
not be necessary; if our build system were sufficiently smart, it  
would determine when such files are out of date and should be  
automatically deleted.  But we do not have such a build system.)

In practice, I tend to redo the steps in doc/HOWTO-BUILD, and if  
something seems askew afterwards, then I will clean out all of the  
build products and start fresh.  One technique I use to find a list  
of files that are not part of the repository (which usually is a list  
of all the build products) is to emit the following subversion command:

% svn status --no-ignore | grep ^[I?] | sed -e s/^.// | xargs echo

-Felix