diff --git a/doc/tutorial/source/getting-started.rst b/doc/tutorial/source/getting-started.rst index 733faaa46..1ddfae662 100644 --- a/doc/tutorial/source/getting-started.rst +++ b/doc/tutorial/source/getting-started.rst @@ -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) diff --git a/doc/tutorial/source/introduction.rst b/doc/tutorial/source/introduction.rst index ca42a0c17..df620a24c 100644 --- a/doc/tutorial/source/introduction.rst +++ b/doc/tutorial/source/introduction.rst @@ -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 diff --git a/doc/tutorial/source/quick-start.rst b/doc/tutorial/source/quick-start.rst index 70cff750a..9f4817ac7 100644 --- a/doc/tutorial/source/quick-start.rst +++ b/doc/tutorial/source/quick-start.rst @@ -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: ::