Omnet ++ installation and various architecture debugging experiences in Windows

The following describes how to use omnet ++ integrated in the msvc6.0 environment on Windows.

1. Install omnet

1. Go to the omnet official website to download the installation program under the Windows platform, the current version is omnetpp-3.2p1-win32;

Download ghostscript,

URL: http://sourceforge.net/project/showfiles.php? Group_id = 1897 & release_id = 202607

2. Install VC. Check "register environment variable" when installing VC"

3. Install ghostscript

4. Install omnet. When the installation progress is reached, the installer will prompt that the gswin 32c.exemust be provided. The gswin32c.exe required by omnetwill be in the bin folder of the ghostscript installation directory.

Note:

The installation path of omnet ++ cannot contain spaces or Chinese characters. Only English characters and numbers are allowed.

Ii. Use of omnet ++ gned

Gned is a network discription language editing and compilation tool used to describe the topology of a simulated network. For the syntax structure of Ned, see omnet manual. See the gnedapplication documentation in this document.

When I learned about omnet, I naturally downloaded a lot of shared architectures on the network, but unfortunately I cannot fully understand them. Let's debug them first. Generally, because the running environment is different, many source codes cannot be compiled directly. Below are some suggestions. change the statement that contains many non-library files to "" To facilitate execution and search for header files. some codes use the STL standard components of VC but do not contain the corresponding library, so that an inexplicable error occurs. 3 It is recommended to add the corresponding header file to the header file.

Using namespace STD;

3. do not contain Chinese or other characters in the file path. Although errors may not occur, they cannot be completely correct, so avoid 4. in a project with a large number of Ned files, the corresponding import Ned file cannot be found during compilation, resulting in various searches, before compilation, you can open each Ned file separately (not in Notepad mode) and open it under omnet. This will automatically identify the file and remind you to find the corresponding source file. In this way, you do not need to search one by one during compilation.