INSTALL 4.3 KB

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