[Openmcl-devel] How to cut down the size of ccl
gb at clozure.com
Thu May 6 08:11:15 PDT 2010
Well, you already mentioned a way to free up 57M. If you need to free more
disk space ....
On an x86 Darwin system (where IIRC the ccl-1.5 directory contains a fresh
checkout, e.g., no fasls):
[src/ccl-1.5] gb at antinomial> du -ms . *
What you need depends on what you want to do.
If you're only interested in running one or the other of the 32-bit and
64-bit versions, you can delete the kernel, .image, and headers directory
for the other word size.
If you're just interested in compiling and running CL code (without using
CCL's FFI), all that you really need are the kernel and .image file.
If you use ASDF and/or ASDF-INSTALL, they're distributed in the tools directory.
If you want to be able to rebuild CCL from source, then you need the directories
that contain sources (compiler, level-0, level-1, lib, library, lisp-kernel, tools,
and xdump); since these sources also use the FFI to access things defined in
the C runtime library, you also need the headers directory for the platform
and its libc subdirectory; the other subdirectories of the headers directory
contain interfaces for Cocoa and other frameworks that you probably can't
The .images contain source location information that can be helpful for
debugging; even if you don't intended to compile the sources on this machine,
having them available makes that information more useful.
Whether the doc, examples, and contrib directories are more or less important
than the disk space that they require is up to you.
On Thu, 6 May 2010, Leo wrote:
> But I mean the diskspace. I know it is ridiculously small. The machine's
> memory is quite large.
> CCL-USER> _
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
More information about the Openmcl-devel