How to handle external dependencies in external message definitions #372
Replies: 3 comments
-
Update: I also tried to place the I tried to edit basilisk's |
Beta Was this translation helpful? Give feedback.
-
I'm assuming you are using Windows? I would ensure that your PATH variable includes the path to these custom support files. |
Beta Was this translation helpful? Give feedback.
-
Thank you for the advice. I am using Linux (Ubuntu 22.10). I tried adding the path to the relevant support file to the |
Beta Was this translation helpful? Give feedback.
-
Hello folks,
I defined an external C++ message definition named in this case
ControlErrorMsgPayload.h
, in the subfoldermsgPayloadDefCpp
of my custom BSK folder following the naming conventions from here http://hanspeterschaub.info/basilisk/Install/buildExtModules.htmlI am using Basilisk 2.2.0. The code of my custom C++ message definition is the following:
Where
ControlError.hpp
is in our codebase so in another folder not related to basilisk.When compiling Basilisk (with
python conanfile.py --pathToExternalModules ../tubix20-lib/adcs/basilisk/
), I am getting the following error, as unsurprisingly, the compiler is not able to findControlError.hpp
:How can I define the path for such external dependencies in external message definitions? For my custom modules, I solved that with
Custom.cmake
CMakefiles, but for message definitions I don't see this possibility.Cheers
Clément
Beta Was this translation helpful? Give feedback.
All reactions