Skip to content
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

Quesiton: Code fail to compile in ROS Melodic #54

Closed
caguero opened this issue Jun 29, 2018 · 3 comments
Closed

Quesiton: Code fail to compile in ROS Melodic #54

caguero opened this issue Jun 29, 2018 · 3 comments

Comments

@caguero
Copy link

caguero commented Jun 29, 2018

Question: I failed to compile the code in master in an Ubuntu Bionic distribution with ROS Melodic because all calls to logWarn, logDebug failed. Here's an example:

In file included from /home/developer/jackal_ws/src/LMS1xx/include/LMS1xx/LMS1xx.h:27:0,
                 from /home/developer/jackal_ws/src/LMS1xx/src/LMS1xx.cpp:36:
/home/developer/jackal_ws/src/LMS1xx/include/LMS1xx/lms_buffer.h: In member function 'void LMSBuffer::readFrom(int)':
/home/developer/jackal_ws/src/LMS1xx/include/LMS1xx/lms_buffer.h:54:7: error: 'logWarn' was not declared in this scope
       logWarn("Buffer read() returned error.");

I have a patch that fixes the issue (essentially adding the CONSOLE_BRIDGE_ prefix to all of them. Do you have any plans for supporting ROS Melodic? Should I just submit a pull request against master? Are you considering a separate release branch for Melodic maybe?

@scpeters
Copy link

scpeters commented Jul 9, 2018

This is related to ros/console_bridge#18; the logWarn and other macros were changed to have a prefix. The old macros were deprecated with new macros added in console_bridge 0.3 (xenial/kinetic), and the old macros were removed in 0.4 (bionic/melodic).

So the patch that @caguero is talking about will fix compiler warnings on (xenial/kinetic), fix compilation on (bionic/melodic), and break compilation on (trusty/indigo).

If you want to keep supporting trusty/indigo, you might want to consider making a new branch.

@FahadRazaKhan
Copy link

Faced the same Error, and fixed it as @caguero said. BTW is there any easy way to it instead of adding prefix in the code?
Thank you.

@tonybaltovski
Copy link
Member

This has been fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants