Hello,
I'm working on OMNET++ and INET based project and I encountered an issue with omnetpp.ini including other INI files and multiple "ned-path" and "load-libs" directives in each INI file. My expectation is that content of "ned-path" and "load-libs" defined in included INI will be joined. Apparently it doesn't happen and I wonder whether it's bug or feature :)
Here's my project configuration (directories tree):
-- OMNET++/
|
-- INET/
|
-- MyFramework/ (something like INET, it provides some common models etc.)
| |
| -- src/
| |
| -- simulations/
| |
| -- omnetpp.ini <- in this INI I specify: "ned-path = ../src:../inet/src" and "load-libs = ../src/MyFramework ../inet/src/INET"
| |
| -- scenarion_a/
| |
| -- omnetpp.ini <- in this INI I include superior omnetpp.ini: "include ../omnetpp.ini"
|
-- MyProject/
|
-- src/
|
-- simulations/
|
-- test_case_based_on_scenario_a/
|
-- omnetpp.ini <- here I do following things:
1. include INI from "scenarion_a" provided by MyFramework: "include ../../MyFramework/simulations/scenarion_a",
2. load NEDs from MyProject/src with: "ned-path = ../src"
3. load libs from MyProject/src with: "load-libs = ../src/MyProject"
I was expecting when I try to run simulation in MyProject/simulatuions/test_case_based_on_scenario_a OMNET++ will join all "ned-path" and "load-libs" directives. Unfortunately it's nod the case and only one ned-path / load-libs directive is interpreted and other are ignored.
Do I do something wrong or my expectation is wrong? I'm going to have many subprojects based on MyFramework, so passing (and maintaining) "-l" and -"n" options to opp_run for each of them will be problematic.