OMNeT++/OMNEST Bug Tracker - OMNeT++
View Issue Details
0000983OMNeT++IDE / C++ developmentpublic2017-01-11 20:002017-02-01 14:03
till 
rhornig 
normalmajoralways
resolvedno change required 
x86-64macOS10.12
5.1pre2 
5.1pre3 
0000983: Metamakemake how to add meta:export-include-path and meta:use-exported-include-paths to oppbuildspec staying compatible
I just saw that I have to add --meta:export-include-path --meta:use-exported-include-paths to .oppbuildspec now to get the includes from e.g. inet in my library and to provide my includes for depending libraries.

How can I do that without breaking compatibility to omnetpp 5.0?

No tags attached.
Issue History
2017-01-11 20:00tillNew Issue
2017-02-01 14:03rhornigNote Added: 0001281
2017-02-01 14:03rhornigStatusnew => resolved
2017-02-01 14:03rhornigFixed in Version => 5.1pre3
2017-02-01 14:03rhornigResolutionopen => no change required
2017-02-01 14:03rhornigAssigned To => rhornig

Notes
(0001281)
rhornig   
2017-02-01 14:03   
Sadly, you can't do that. There are several breaking changes between 5.0 and 5.1 so keeping the project to build with both is not feasible.

OMNET 5.1 will require a new version of INET (3.5) anyway. Until then you should manually add the include folder of the base projects in makefrag. Once we release omnet 5.1 and and INET 3.5 you can replace that with the above meta options. (i.e. INET 3.5 will come with --meta:export-include-path)