Changes between Version 2 and Version 3 of tools


Ignore:
Timestamp:
11/19/07 17:19:58 (12 years ago)
Author:
norris
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • tools

    v2 v3  
    2020 
    2121If you are interested in contributing to our development, please email [mailto:norris@mcs.anl.gov Boyana Norris]. 
     22 
     23== Usage == 
     24 
     25Using the new contractor-based build system is very easy. Instead of the usual 'configure, make, install' scenario you now have only two steps (one if you let the system automatically configure, in which case you can omit the first step). 
     26 
     27{{{ 
     28$ cd cca-tools-contractor 
     29$ ./contract.py --configure 
     30... 
     31$ ./contract.py 
     32...  
     33}}} 
     34 
     35For more control over the build, you can set your own configuration options manually to override the defaults. To see the list of available options, pass the --configure-show argument, which also shows you the arguments passed to configure on the last invokation. 
     36 
     37{{{ 
     38$ ./contract.py --configure-show 
     39... 
     40$ ./contract.py --configure python=/sw/bin/python2.5 fortran90= 
     41... 
     42}}} 
     43 
     44As seen above, to unset an option just leave the right side of the assignment blank. The example above sets the path to the Python interpreter to use in babel and ccaffeine and disables Fortran 90 support. 
     45 
     46Specific stages can be built easily using the new build system. There are a couple of special stages of note: the default target (called when no arguments are passed), the global clean target (to clean everything), and the per-package all and clean targets. 
     47 
     48{{{ 
     49$ ./contract.py babel/make 
     50... 
     51$ ./contract.py babel/all 
     52... 
     53$ ./contract.py clean 
     54...  
     55}}}