Closed gseqBE closed 1 year ago
@Acuadros95 is this something that could be fixed. Thanks!
Hi @gseqBE,
For some reason, the generated code for the test_msgs
package does not include the extern "C"
guards to fix name mangling on c++.
We will take a closer look at this issue, but as those messages are used only for testing purposes, we can just leave them out of our build process. Please try to build again with this PR branch: https://github.com/micro-ROS/micro_ros_zephyr_module/pull/99
Thanks @Acuadros95 . I still seem to get the build errors in fix/cpp_build. Were you able to try with
CONFIG_CPLUSPLUS=y
CONFIG_LIB_CPLUSPLUS=y
in prj.conf?
Were you able to try with
Yes. Which errors do you get?
Adding the build log. All I did was add the two cpp config lines in prf.conf. build.log
Well, test_msgs
is still being build on your log. Can you try on a clean environment with the merged fix?
@Acuadros95 I'm away on a work trip, please give me till this Friday to test. Thank you.
@Acuadros95
Confirming that merged fix in humble branch works for me, with the two zephyr CPP flags.
Note that my board is a h743zi: west build -b nucleo_h743zi .
For the default west build -b disco_l475_iot1 .
i get an SRAM error with the flags, but someone with those flags will be using a higher SRAM chip anyway.
ws/zephyr-sdk-0.14.2/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.bfd: zephyr/zephyr_pre0.elf section
noinit' will not fit in region SRAM'
Thanks for the help. Issue can close.
Hello, Our code base is cpp based and works well with the non-module style of microros on zephyr. However, with this repo(module based), I get build errors when the following two flags are added to prj.conf: If the below two flags are removed, the default project compiles ok.
Steps to reproduce the issue
Expected behavior
Build succeeds.
Actual behavior
Build failure
build_log.txt
Additional information