F5/unison
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: Update stale tutorial information

Browse Source
This commit is contained in:
Tom Henderson
2022-04-16 15:18:50 -07:00
parent 44c85d30ca
commit 81d5efcc39
3 changed files with 2 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/tutorial/source/getting-started.rst
View File

@@ -76,7 +76,7 @@ are needed to get started with |ns3|:
============ ===========================================================
Prerequisite Package/version
============ ===========================================================
C++ compiler ``clang++`` or ``g++`` (g++ version 7 or greater)
C++ compiler ``clang++`` or ``g++`` (g++ version 8 or greater)
Python ``python3`` version >=3.6
CMake ``cmake`` version >=3.10
Build system ``make``, ``ninja``, ``xcodebuild`` (XCode)

10
doc/tutorial/source/introduction.rst
View File

@@ -112,16 +112,6 @@ reasons:
Some limitations found in |ns2| (such as supporting multiple types of
interfaces on nodes correctly) have been remedied in |ns3|.
|ns2| has a more diverse set of contributed modules than does |ns3|, owing to
its long history. However, |ns3| has more detailed models in several
popular areas of research (including sophisticated LTE and WiFi models),
and its support of implementation code admits a very wide spectrum
of high-fidelity models. Users may be surprised to learn that the
whole Linux networking stack can be encapsulated in an |ns3| node,
using the Direct Code Execution (DCE) framework. |ns2|
models can sometimes be ported to |ns3|, particularly if they have been
implemented in C++.
If in doubt, a good guideline would be to look at both simulators (as
well as other simulators), and in particular the models available
for your research, but keep in mind that your experience may be better

2
doc/tutorial/source/quick-start.rst
View File

@@ -102,7 +102,7 @@ Once you have obtained the source either by downloading a release or by
cloning a Git repository, the next step is to
configure the build using the *CMake* build system. There
are several options to control the build, but enabling the example programs
and the tests, for a default debug build profile (with debugging symbols
and the tests, for a default build profile (with asserts enabled and
and support for |ns3| logging) is what is usually done at first:
::