![]() doxygen-no-build, -docset: probably require two targets per command, one depending on the libraries/executables and other not depending on them -enable-sudo: not implemented. ![]() run, -run-no-build, -visualize, -gdb, -valgrind: ns3waf.py -run|-run-no-build|-visualize|-gdb|-valgrind -command-template, -pyrun and -pyrun-no-build: in the works for ns3waf. ![]() enable-gcov and -lcov-report : NS3_COVERAGE=ON|OFF -lcov-zerocounters: NS3_COVERAGE_ZERO_COUNTERS=ON|OFF -no-task-lines: depend on the buildsystem, not sure CMake can silence this. I can rewrite the docs properly depending on the demand/feedback.ĮDIT: Adding a list of supported switches and their mapping to CMake. It will automatically generate the cache and load the targets to build/run/debug. Just open the ns-3-dev folder, right click the CMakeLists file and click to load the CMake project. From IDEs that support CMake projects (e.g. Targets to build/run/debug should be available for libraries/tests/examples/docs if enabled. Then open the IDE and load the Makefile in the cmake cache folder. Same instructions for command line, but choosing "Unix Makefiles" or "MinGW Makefiles" as the CMake generator (-G). ns3 configure -G Ninja, the CMake project will be configured to use the specified generator (in this case Ninja)įrom IDEs that do not support CMake projects (e.g. ns3 -gdb|-valgrind -run example, it will execute all the previous steps but execute the program through gdb|valgrind ns3 -run example, it will refresh the CMake cache, then build and then run the example If you specify a target to be built (either a module or an executable), it will get built along with its dependencies (e.g./ns3waf build wifi) ns3 build, the entire project will be built. ns3 configure, the CMake project will be configured with the default settings
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |