Changeset 13056

Oct 20, 2009, 8:05:58 PM (10 years ago)

Update a little (no more CVS...). Also mention that Snow Leopard systems
need the optional Xcode 10.4 support.

1 edited


  • trunk/source/doc/src/build.xml

    r12330 r13056  
    6969          image</primary></indexterm> <glossterm linkend="lisp_image">heap
    7070        image</glossterm> is a file that can be quickly mapped into a
    71       process' address space. Conceptually, it's not too different
     71      process's address space. Conceptually, it's not too different
    7272      from an executable file or shared library in the OS's native
    73       format (ELF orMach-O/dyld format); for historical reasons,
     73      format (ELF or Mach-O/dyld format); for historical reasons,
    7474      &CCL;'s own heap images are in their own (fairly simple)
    7575      format. The term <literal>full heap image</literal> refers to a
    238238  <sect1 id="Setting-Up-to-Build">
    239239    <title>Setting Up to Build</title>
    240     <para>There are currently three versions of &CCL; that you
    241       might want to use (and therefore might want to build from
     240    <para>At a given time, there are generally two versions of &CCL; that
     241    you might want to use (and therefore might want to build from
    242242      source):</para>
    243243    <itemizedlist>
    244       <listitem><para>Version 1.0 - the more stable version</para></listitem>
    245       <listitem><para>Version 1.1 - the more recent version, which
    246           runs on more platforms (including x86-64 platforms) and
    247           supports Unicode</para></listitem>
    248           <listitem><para>Version 1.2 - supports (at least) all of the
    249               features and platforms of 1.1, but is distributed and updated
    250               differently</para></listitem>
     244      <listitem><para>The released version</para></listitem>
     245      <listitem><para>The development version, called the "trunk", which
     246      may contain both interesting new features and interesting new bugs
     247      </para></listitem>
    251248    </itemizedlist>
    252     <para>All versions are available for download from the &CCL;
    253       website in the form of archives that contain everything you need
    254       to work with &CCL;, including the complete sources, a full
    255       heap image, and the foreign-function interface database.</para>
    256     <para>Version 1.0 archives are named
    257       <literal>openmcl-</literal><replaceable>platform</replaceable><literal>-all-1.0.tar.gz</literal>,
    258       where <replaceable>platform</replaceable> is either
    259       <literal>darwinppc</literal>, <literal>darwinppc64</literal>, or
    260       <literal>linuxppc</literal>.  Because version 1.0 is no longer
    261       undergoing active development, you won't ever need to update
    262       these sources.</para>
    263     <para>Version 1.1 archives are named
    264       <literal>openmcl-</literal><replaceable>platform</replaceable><literal>-snapshot-</literal><replaceable>yymmdd</replaceable><literal>.tar.gz</literal>,
    265       where <replaceable>platform</replaceable> is either
    266       <literal>darwinppc</literal>, <literal>darwinx8664</literal>,
    267       <literal>linuxppc</literal>, <literal>linuxx8664</literal>, or
    268       <literal>freebsdx8664</literal>, and where
    269       <replaceable>yymmdd</replaceable> is the year, month, and day
    270       the snapshot was released.</para>
    271     <para>Because version 1.1 is undergoing active development,
    272       there may be times when you want to get sources that are more
    273       recent than the most recent snapshot and use them to build
    274       yourself a new bleeding-edge &CCL;.  In that case, you should
    275       download and install the latest snapshot, and then update your
    276       sources via CVS.  At that point you can rebuild and you'll have
    277       the latest and greatest &CCL;.  The snapshot has CVS
    278       working-copy information in it, so all you need to do to update
    279       is</para>
    280     <programlisting>
    281 $ cd ccl
    282 $ cvs login             # password is "cvs"
    283 # this step only needs to be done once,
    284 # that'll store the trivially encrypted
    285 # password in ~/.cvspas
    286 $ cvs update
    287     </programlisting>
    288     <para>Unless you tell it to, cvs won't delete ("prune") empty
    289       directories or create new ones when the repository changes.
    290       It's generally a good habit to use</para>
    291     <programlisting>
    292 $ cvs update -d -P      # create dirs as needed, prune empty ones
    293     </programlisting>
    294     <para>Version 1.2 archives follow naming conventions that are
    295       similar to those used by 1.0 (though more platforms are supported.)
    296       However, rather than containing CVS working-copy information, the
    297       1.2 (and, presumably, later) archives contain metainformation used
    298       by the Subversion (svn) source-code control system.</para>
    299     <para>Subversion client programs are pre-installed on OSX 10.5 and
     249    <para>All versions are available for download from via
     250    the Subversion source control system.</para>
     251    <para>
     252      For example, to get a released version (1.3 in this example),
     253      use a command like:
     254      <programlisting>
     255        svn co
     256      </programlisting>
     257    </para>
     258    <para>
     259      To get the trunk version, use:
     260      <programlisting>
     261        svn co
     262      </programlisting>
     263    </para>
     264    <para>
     265      Change the "xxx" to one of the following names:
     266      <literal>darwinx86</literal>,
     267      <literal>linuxx86</literal>,
     268      <literal>freebsdx86</literal>,
     269      <literal>solarisx86</literal>,
     270      <literal>window</literal>,
     271      <literal>linuxppc</literal>,
     272      or
     273      <literal>darwinppc</literal>.
     274    </para>
     275    <para>
     276      In the case of released versions, there may also be tar archives
     277      available.  See the <ulink url="">Clozure CL
     278      Trac</ulink> for details.
     279    </para>
     280    <para>Subversion client programs are pre-installed on Mac OS X 10.5 and
    300281      later and are typically either pre-installed or readily available
    301282      on Linux and FreeBSD platforms.  The <ulink url="">Subversion web page</ulink> contains links to subversion client programs
    302       for many platforms; users of OSX versions 10.4 and earlier can also
     283      for many platforms; users of Mac OS X 10.4 can also
    303284      install Subversion clients via Fink or MacPorts.</para>
    404385            tools, the better; some versions of gcc 3.x on Linux have
    405386            difficulty compiling some of the kernel source code correctly
    406             (so gcc 4.0 should be used, if possible.)  On OSX, the
    407             versions of the tools distributed with XCode should work fine;
     387            (so gcc 4.0 should be used, if possible.)  On Mac OS X, the
     388            versions of the tools distributed with Xcode should work fine;
    408389            on Linux, the versions of the tools installed with the OS (or
    409390            available through its package management system) should work
    413394            GNU version of the m4 macroprocessor (called
    414395            <literal>gm4</literal> on FreeBSD) should be installed.
    416396          </para>
     397          <note><para>In order to build the lisp kernel on Mac OS X
     398          10.6 Snow Leopard, you must install the optional 10.4
     399          support when installing Xcode.</para>
     400          </note>
    417401    </sect2>
Note: See TracChangeset for help on using the changeset viewer.