Helix SwarmHelix Swarm

README.html

  • //
  • guest/
  • chris_comparini/
  • jam_sample/
  • sample/
  • rootless/
  • README.html #1
  • View
  • Commits
  • Open Download .zip Download (3 KB) 
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Final//EN">
  2. <HTML>
  3.  <HEAD>
  4.   <TITLE>Rootless Jam example</TITLE>
  5.  </HEAD>
  6.  
  7.  <BODY>
  8.  
  9.  <p> The <a href="../simple">simple</a> and <a href="../abstract">abstract</a>
  10.      examples assume a single, one-part or hierarchical project layout.  This
  11.      example illustrates one way to use Jam to build a project which consists
  12.      of several "parallel" projects with no particular "root" directory or
  13.      project.
  14.  
  15.  <p> Incidentally, we use c++ on this project instead of c.
  16.  
  17.  <p> For this example, we hypothesize a project consisting of
  18.      several separate sub projects, each of which may be targeted
  19.      to a particular operating system. 
  20.      We have the following directories:
  21.  
  22.    <ul>
  23.      <li>shared:    Code common to all platforms.
  24.      <li>mac:       Source code for the Macintosh client
  25.      <li>pcwin:     Source code for the Windows client
  26.      <li>xwindows:  Source code for the Unix/XWindows client
  27.      <li>server:    Server source code
  28.      <li>all-bin:   Target directory for builds.  This contains no
  29.                     source code, but does contain a Jamfile.
  30.    </ul>
  31.  
  32.  <p> The server runs on Windows NT and on various Unix
  33.      platforms<sup><a href="#fn1">*</a></sup>.  The mac, pcwin and xwindows
  34.      directories contain code for the various clients.  All the various
  35.      servers and clients rely on code in the "shared" directory.
  36.      Finally, the all-bin directory contains a Jamfile which determines
  37.      which set of sub projects to build for a given platform.  As usual,
  38.      Jam can be run in any of the sub directories; only the sub project
  39.      in that directory will be compiled.
  40.  
  41.  <p> The point of this arrangement is it allows the separate sub projects
  42.      to be very independant.  For example, if you are working on the Mac
  43.      client, you need only the "mac" and "shared" directories.  Alternately,
  44.      let's say you want to build all the sub projects which are appropriate
  45.      to the platform on (and for) which you are compiling (for example,
  46.      when building a release).  In this case, you would get all the sub
  47.      projects from <a href="//www.perforce.com">your version control system</a>
  48.      and run Jam in the all-bin directory.  The Jamfile there controls
  49.      which sub projects go into the package for a release on a given
  50.      operating system.
  51.  
  52.  <p>Things to try:
  53.    <ul>
  54.      <li>  Run Jam from the server directory.  The server and related "db"
  55.            library will be built and placed in a subdirectory of ../all-bin/,
  56.            and a "test bed" for the server will be created in the test_dir
  57.            directory.  <b><i>more here</i></b>
  58.    </ul>
  59.  
  60.  <hr>
  61.     <a name="fn1">*</a>Actually, each "client" or "server" application
  62.     just prints a version string and exits, and should probably run on just
  63.     about anything, but let's pretend.
  64.  </BODY>
  65. </HTML>
  66.  
# Change User Description Committed
#1 4438 Chris Comparini Sample jam projects.
 "rootless" documentation still needs work. 		21 years ago