8000 Build errors not displayed automatically when using `colorgcc` · Issue #361 · catkin/catkin_tools · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Build errors not displayed automatically when using colorgcc #361
Open
@dornhege

Description

@dornhege

System Info

  • Operating System: Trusty
  • Python Version: 2.7.6
  • Version of catkin_tools: 0.4.2
  • ROS Distro: indigo

Build / Run Issue

Whenever there is a compiler error (g++) with the current version of catkin tools it is not displayed, i.e., I get:

Starting  >>> test_pkg                                                                                 
_______________________________________________________________________________________________________
Errors     << test_pkg:make ...rosws/test/logs/test_pkg/build.make.002.log                 
make[2]: *** [CMakeFiles/test_pkg_node.dir/src/main.cpp.o] Error 1
make[1]: *** [CMakeFiles/test_pkg_node.dir/all] Error 2
make: *** [all] Error 2
cd ...rosws/test/build/test_pkg; catkin build --get-env test_pkg | catkin env -si  /usr/bin/make --jobserver-fds=6,7 -j; cd -
.......................................................................................................

The listed log file correctly contains the build errors.

rosws/test/src/test_pkg/src/main.cpp:5:2: error: #error Test
 #error Test
  ^
make[2]: *** [CMakeFiles/test_pkg_node.dir/src/main.cpp.o] Error 1
make[1]: *** [CMakeFiles/test_pkg_node.dir/all] Error 2
make: *** [all] Error 2

catkin build -v also shows the errors directly together with all the other verbose-ness.

I believe that not showing errors or warnings is not the intended behavior and these should show in the build output.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0