README
changeset 1786 c88914465031
parent 956 cf63e1cc64be
child 2841 eed8d933cdf0
equal deleted inserted replaced
1785:04704f042c03 1786:c88914465031
    82 The current codebase is expected to build and run on the
    82 The current codebase is expected to build and run on the
    83 following set of platforms:
    83 following set of platforms:
    84   - linux x86 gcc 4.2, 4.1, and, 3.4.
    84   - linux x86 gcc 4.2, 4.1, and, 3.4.
    85   - linux x86_64 gcc 4.0
    85   - linux x86_64 gcc 4.0
    86   - MacOS X ppc and x86
    86   - MacOS X ppc and x86
       
    87   - cygwin
    87 
    88 
    88 The current codebase is expected to fail to build on
    89 The current codebase is expected to fail to build on
    89 the following platforms:
    90 the following platforms:
    90   - gcc 3.3 and earlier
    91   - gcc 3.3 and earlier
    91   - optimized builds on linux x86 gcc 4.0 
    92   - optimized builds on linux x86 gcc 4.0 
    92   - cygwin
       
    93 
    93 
    94 Other platforms may or may not work: we welcome 
    94 Other platforms may or may not work: we welcome 
    95 patches to improve the portability of the code to these
    95 patches to improve the portability of the code to these
    96 other platforms.
    96 other platforms.
    97 
    97 
   100 
   100 
   101 On recent Linux systems, once you have built ns-3, it 
   101 On recent Linux systems, once you have built ns-3, it 
   102 should be easy to run the sample programs with the
   102 should be easy to run the sample programs with the
   103 following command:
   103 following command:
   104 
   104 
   105 ./waf --run simple-p2p
   105 ./waf --run simple-point-to-point
   106 
   106 
   107 That program should generate a simple-p2p.tr text 
   107 That program should generate a simple-point-to-point.tr text 
   108 trace file and a set of simple-p2p-xx-xx.pcap binary
   108 trace file and a set of simple-point-to-point-xx-xx.pcap binary
   109 pcap trace files, which can be read by tcpdump.
   109 pcap trace files, which can be read by tcpdump.
   110 
   110 
   111 5) Getting access to the ns-3 documentation
   111 5) Getting access to the ns-3 documentation
   112 -------------------------------------------
   112 -------------------------------------------
   113 
   113 
   114 Once you have verified that your build of ns-3 works by running
   114 Once you have verified that your build of ns-3 works by running
   115 the simple-p2p example as outlined in 4) above, it is
   115 the simple-point-to-point example as outlined in 4) above, it is
   116 quite likely that you will want to get started on reading
   116 quite likely that you will want to get started on reading
   117 some ns-3 documentation. 
   117 some ns-3 documentation. 
   118 
   118 
   119 All of that documentation should always be available from
   119 All of that documentation should always be available from
   120 the ns-3 website: http:://www.nsnam.org/ but we
   120 the ns-3 website: http:://www.nsnam.org/ but we