Project

General

Profile

Actions

Bug #156

closed

ros compilation

Added by Nicolas Staub about 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-

Description

when compiling modules for ros I often get stuck for long time with:

"the rosdep view is empty: call 'sudo rosdep init' and 'rosdep update' "

but by rosdep is not empty an up to date, would be nice to get shorten the time it struggles, especially when updating a lots of modules


Related issues

Has duplicate robotpkg - Bug #78: Building optitrack-genom3 on 12.04 machine with groovyClosedActions
Actions #1

Updated by Anthony Mallet about 4 years ago

  • Tracker changed from Feature to Bug
  • Project changed from genom3 to robotpkg
Actions #2

Updated by Anthony Mallet about 4 years ago

  • Has duplicate Bug #78: Building optitrack-genom3 on 12.04 machine with groovy added
Actions #3

Updated by Anthony Mallet about 4 years ago

when compiling modules for ros I often get stuck for long time with:

You're not 'stuck'. The message itself takes no time to display.
It's just ros compilation that is awfully slow, but the error message
is not related.

"the rosdep view is empty: call 'sudo rosdep init' and 'rosdep update' "

but by rosdep is not empty an up to date, would be nice to get shorten
the time it struggles, especially when updating a lots of modules

I know about that, but I cannot do anything to prevent it.

This is a misleading error from ros, that misinterpret the fact that
his database is empty. robotpkg does not use this database to compile
the ros components, but it still uses some features of the scripts in
question.

The error message is hardcoded in a script, I could not find a way to
disable it. That said, it's just painful for the eyes but has no
consequence.

Actions #4

Updated by Anthony Mallet almost 4 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF