You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When restructuring my project I tried to import a defs.msg with import common.defs into linklayer/linkLayerFrame.msg . defs.msg contains some definitions. The project looked like so:
I had a problem with the message compiler, which would give the following error compilling
linkLayerFrame.msg Error: cannot resolve import 'common.defs'
Which was being compiled with: opp_msgc --msg6 -s _m.cc -MD -MP -MF ../out/gcc-release/src/linklayer/linkLayerFrame_m.h.d -I../../inet/src linklayer/linkLayerFrame.msg To Reproduce
Attached project: msg_import_bug.zip
Does not build unless ../src is added to C/C++ Build -> Paths and Symbols -> Includes
Problem
It is implied that, like .ned files messages will be included if they are within the directory structure of the same package. But this is not the case and it is not explained anywhere that the C/C++ include paths are relevant for the msgtool.
The text was updated successfully, but these errors were encountered:
Platform
Describe the bug
When restructuring my project I tried to import a
defs.msg
withimport common.defs
intolinklayer/linkLayerFrame.msg
.defs.msg
contains some definitions. The project looked like so:I had a problem with the message compiler, which would give the following error compilling
linkLayerFrame.msg
Error: cannot resolve import 'common.defs'
Which was being compiled with:
opp_msgc --msg6 -s _m.cc -MD -MP -MF ../out/gcc-release/src/linklayer/linkLayerFrame_m.h.d -I../../inet/src linklayer/linkLayerFrame.msg
To Reproduce
Attached project:
msg_import_bug.zip
Does not build unless
../src
is added to C/C++ Build -> Paths and Symbols -> IncludesProblem
It is implied that, like
.ned
files messages will be included if they are within the directory structure of the same package. But this is not the case and it is not explained anywhere that the C/C++ include paths are relevant for the msgtool.The text was updated successfully, but these errors were encountered: