-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
copilot-core
: ROS, FPrime and Copilot backends expect handlers to be named differently
#130
Comments
Description The Spec to Copilot translator and the FPrime and ROS translators generate handler names in slightly different ways. The latter adds an extra Type
Additional context None. Requester
Method to check presence of bug Compiling the following trivial spec with both the ROS and the Copilot backends should produce files that can be compiled together without edits:
Expected result Compiling the spec above using both the Copilot and the ROS backends should produce a ROS app that includes the monitors and compiles correctly without edits. Desired result Compiling the spec above using both the Copilot and the ROS backends should produce a ROS app that includes the monitors and compiles correctly without edits. Proposed solution Modify FPrime and ROS app generators to not include the extra Further notes None. |
copilot-core
: ROS, FPrime and Copilot backends expect handlers to be named differently
Change Manager: Confirmed that the issue exists. |
Technical Lead: Confirmed that the issue should be addressed. |
Technical Lead: Issue scheduled for fixing in Ogma 1.3. Fix assigned to: @ivanperez-keera. |
The Copilot, FPrime and ROS backends do not use the same name for the handler names. In one case, an extra "prop" is added to the name, which makes the resulting Copilot code not directly usable from FPrime / ROS without edits. This commit modifies the FPrime and ROS backends so that the handler names do not contain the additional "prop", making them match the Copilot backend.
Implementor: Solution implemented, review requested. |
Change Manager: Verified that:
|
Change Manager: Implementation ready to be merged. |
Issue: Linker Error During Compilation of ROS Application
Summary
I am encountering a linker error towards the end of compiling a ROS application, specifically with undefined references to various handlers. This issue is preventing the successful build of the copilot package.
Details
The compilation process fails with the following linker error:
collect2: error: ld returned 1 exit status
Affected Environment
Steps to Reproduce
colcon build
.Expected Behavior
The application should compile successfully without any linker errors.
Actual Behavior
The build process fails with a linker error related to undefined references to handlers.
Additional Context
Terminal output showcasing the error:
Please note that the undefined reference to "halt" can be ignored for the purposes of this issue.
Request for Assistance
Any insights or suggestions on how to resolve these undefined reference errors would be greatly appreciated. If further information or clarification is needed, please let me know.
The text was updated successfully, but these errors were encountered: