Revision history [back]

Thanks for everyone's help.

I finally find where the problem is.

It is possible in catakin workspace to use the msg defined in rosbuild package, just include the header file generated by the original msg file will work.

And the error occurred because I want the function return an int value.

I checked some working package and found I should not do that, the callback function should be a void function.

Then it works after I change it to

int callback(const tld_msgs::BoundingBox &data) { }

Thanks for everyone's help.

I finally find found where the problem is.

It is possible in catakin workspace to use the msg defined in rosbuild package, just include the header file generated by the original msg file will work.is okay.

And the error occurred because I want the function return an int value.

I checked some working package and found I should not do that, the callback function should be a void function.

Then it works after I change it to

int callback(const tld_msgs::BoundingBox &data) { }

Thanks for everyone's help.

I finally found where the problem is.

It is possible in catakin workspace to use the msg defined in rosbuild package, just include the header file generated by the original msg file is okay.

And the error occurred because I want the function return an int value.

I checked some working package and found I should not do that, the callback function should be a void function.

Then it works compiles with no error after I change it to

int void callback(const tld_msgs::BoundingBox &data) { }