ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

build warning for kinetic release - "missing whitespace after the macro name"

asked 2017-08-03 07:36:44 -0600

peter gravatar image

updated 2017-08-04 11:00:33 -0600


while preparing one of our packages for release I encountered a strange problem. While building for ros indigo and jade worked as supposed (no errors), there are warnings for ros kinetic and lunar, which in turn leads to an "unstable" build state. Before releasing to kinetic, i would like to get rid of the warnings.

It seems as the warning message "missing whitespace after the macro name" is related to some macro passed via command-line:
+ e.g.

The package is hosted here: +

The build-results can be found here:
+ indigo:
+ kinetic:

+ 12.1. build workspace in isolation and install
+ ...
+ 00:06:42.344 Scanning dependencies of target pcdfilter_pa
+ 00:06:42.361 [ 4%] Building CXX object CMakeFiles/pcdfilter_pa.dir/src/pcdfilter_pa.cpp.o
+ 00:06:42.370 <command-line>:0:15: warning: missing whitespace after the macro name
+ 00:06:43.034 [ 8%] Building CXX object CMakeFiles/pcdfilter_pa.dir/src/pcdfilter_pa_parameter.cpp.o
+ 00:06:43.043 <command-line>:0:15: warning: missing whitespace after the macro name
+ 00:06:43.609 [ 12%] Building CXX object CMakeFiles/pcdfilter_pa.dir/src/pcdfilter_pa_filter.cpp.o
+ 00:06:43.621 <command-line>:0:15: warning: missing whitespace after the macro name
+ ...

In contrast a similar package is build stable for all releases:
+ indigo:
+ kinetic:

Thank you for your help in advance

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2018-01-04 08:33:57 -0600

peter gravatar image

I finally found the core of the problem: During the make-process the CXX-Flag "-DDISABLE_LIBUSB-1.0" will be set in the file "flags.make". This flag has a bad name as it consists of a "-" Symbol. The file itself was created during the cmake-process based on the added definitions.

The solution was to remove the bad named macro within the "CMakeLists.txt" file be adding

See also link text

Greetings Peter

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2017-08-03 07:36:44 -0600

Seen: 1,235 times

Last updated: Jan 04 '18