Changeset 16 for trunk


Ignore:
Timestamp:
02/11/08 18:57:11 (4 years ago)
Author:
dom
Message:

Minimal README files for new setup

Location:
trunk
Files:
1 added
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/README

    r7 r16  
    11EXTREME FORGE 
    22 
    3 http://www.extremeforge.net 
     3http://extremeforge.net 
    44 
    55The aims of this software are: 
     
    1919 
    2020Erlang/OTP R11B4 or above. 
     21Cf. http://www.erlang.org 
    2122 
    2223Installation 
     
    2425 
    2526Download the tarball, unpack to any convenient location. 
    26 Change to the ./ebin subdirectory, then 
    27 start an erlang shell in distributed mode, e.g.: 
     27Change to the directory to which you unpacked. 
     28From the shell, run the 'install' escript: 
    2829 
    29 % erl -sname forge 
     30% ./install 
    3031 
    31 Then, from the erlang shell prompt, first compile: 
    32  
    33 1> make:all(). 
    34  
    35 then run the tests to ensure that Extreme Forge is working on your platform: 
    36  
    37 2> xpdojo:test_files(".."). 
    38  
    39 After some output (including process crashes, they are part of the 
    40 testing process), you should get a last line of output like this: 
    41  
    42 [{acceptance,39,39},{unit,101,101},{modules,27,27}] 
    43  
    44 This means that all unit and acceptance tests have passed. If the 
    45 two numbers following each phase (modules, unit, acceptance) are 
    46 different from each other, some things are not working as expected. 
    47  
    48 Using 
    49 ----- 
    50  
    51 You can now test any source tree of your own in the same way: 
    52  
    53 3> xpdojo:test_files("/some/path/to/source"). 
    54  
    55 Or, for a more interesting experience, run the continuous testing 
    56 server, e.g.: 
    57  
    58 4> Pids = testing_server:start("/some/path/to/source", "/tmp/log.txt"). 
    59  
    60 Then, "tail -f /tmp/log.txt" from shell or an emacs compilation buffer 
    61 to view the output. 
    62  
    63 To stop the testing_server: 
    64  
    65 5> testing_server:stop(Pids). 
    66  
    67 Read src/test_files_acceptance.erl for more details (such as 
    68 defining your own rules for detecting unit and acceptance tests). 
     32This should print out some lines, ending with "done". 
    6933 
    7034LEGAL MATTERS 
    7135------------- 
    7236 
    73 The software contained herein is: 
    74  
    75 Copyright (c) 2004-2007 Dominic Williams, Nicolas Charpentier, 
    76 Fabrice Nourisson, Jacques Couvreur, Virgile Delecolle. 
    77 All rights reserved. 
    78  
    79 Redistribution and use in source and binary forms, with or without 
    80 modification, are permitted provided that the following conditions are 
    81 met: 
    82  
    83 * Redistributions of source code must retain the above copyright 
    84   notice, this list of conditions and the following disclaimer. 
    85 * Redistributions in binary form must reproduce the above copyright 
    86   notice, this list of conditions and the following disclaimer in the 
    87   documentation and/or other materials provided with the distribution. 
    88 * The names of the authors may not be used to endorse or promote 
    89   products derived from this software without specific prior written 
    90   permission. 
    91  
    92 THIS SOFTWARE IS PROVIDED BY THE AUTHORS "AS IS" AND ANY EXPRESS OR 
    93 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
    94 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 
    95 DISCLAIMED. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY DIRECT, 
    96 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 
    97 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 
    98 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 
    99 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 
    100 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 
    101 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 
    102 POSSIBILITY OF SUCH DAMAGE. 
     37See the file COPYING located in the src directory. 
Note: See TracChangeset for help on using the changeset viewer.