forked from inet-framework/inet
-
Notifications
You must be signed in to change notification settings - Fork 1
/
INSTALL
108 lines (76 loc) · 4.32 KB
/
INSTALL
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
INSTALLATION INSTRUCTIONS
=========================
The INET Framework can be compiled on any platform supported by OMNeT++.
PREREQUISITES
You should have a working OMNeT++ installation.
NOTE TO GIT USERS: If you are wondering why the showcases/ and tutorials/
directories are empty, jump forward to the 'Note to Git users' section
of this file.
General
-------
1. Make sure your OMNeT++ installation works OK (e.g. try running the samples)
and it is in the path (to test, try the command "which nedtool"). On
Windows, open a console with the "mingwenv.cmd" command. The PATH and other
variables will be automatically adjusted for you. Use this console to compile
and run INET.
2. Extract the downloaded tarball into a directory of your choice (usually into your
workspace directory, if you are using the IDE). NOTE: The built-in Windows
archiver has bugs and cannot extract the file correctly. Use some other archiver
or do it from command line (tar xvfz inet-yyyymmdd-opp4-src.tgz)
If you are building from command line:
--------------------------------------
3. Change to the INET directory.
4. Type "make makefiles". This should generate the makefiles for you automatically.
5. Type "make" to build the inet executable (release version). Use "make MODE=debug"
to build debug version.
6. You can run specific examples by changing into the example's directory and executing "./run"
If you are using the IDE:
-------------------------
3. Open the OMNeT++ IDE and choose the workspace where you have extracted the inet directory.
The extracted directory must be a subdirectory of the workspace dir.
4. Import the project using: File | Import | General | Existing projects into Workspace.
Then select the workspace dir as the root directory, and be sure NOT to check the
"Copy projects into workspace" box. Click Finish.
5. Open the project (if already not open) and wait until the indexer finishes.
Now you can build the project by pressing CTRL-B (Project | Build all)
6. To run an example from the IDE open the example's directory in the Project Explorer view,
find the corresponding omnetpp.ini file. Right click on it and select Run As / Simulation.
This should create a Launch Configuration for this example.
If the build was successful, you may try running the demo simulations.
Change into examples/ and type "./rundemo".
Note:
-----
- by default INET is creating a shared library (libINET.dll, libINET.so etc.)
in the "src" directory. To use the shared library you can use the "opp_run"
command to load it dynamically. Open the "src/run_inet" script to see how
to do it.
- If you add/remove files/directories later in the src directory, you MUST
re-create your makefile. Run "make makefiles" again if you are building
from the command line. (The IDE does it for you automatically)
Note to GIT users:
------------------
If you want to check out INET directly from the repository, we recommend using the
$ git clone --recursive [email protected]:inet-framework/inet.git
command, because the INET repository contains git submodules. If you forget to specify
--recursive, you can initialize those submodules with:
$ git submodule update --init
To make the installation simple, the GIT repo contains all IDE configuration files.
If you make local changes in the IDE you may need to disable the change tracking on
those files, so GIT will not insist committing those changes back on your next commit.
You can use the _scripts/track-config-files-[on/off] scripts to enable/disable the
change tracking.
To further ease the merging/rebasing operation the .cproject .nedfolders .oppbuildspec .project
files are configured to be resolved using the 'ours' merge strategy. Depending on your
GIT version, you may need to enable the 'ours' merge driver for the project:
$ git config merge.ours.driver true
VoIPTool feature
================
VoIPTool has only been tested on Linux. This does not mean it won't work on other
systems, but your mileage may vary on getting it up and running.
PREREQUISITES.
VoIPTool requires a "devel" package of the avcodec library (part of FFmpeg)
to be installed on your system. On Ubuntu, this package can be installed with the
following command:
$ sudo apt-get install libavcodec-dev
$ sudo apt-get install libavformat-dev
The package name and installation command may vary for other Linux systems.