Revision history [back]

It seems there was/is an issue with the roscopter install instructions (h**ps://github.com/epsilonorion/roscopter/wiki):

... * Navigate back to repo folder * Checkout mavlink using submodule (shown below), or create a symlink to an existing mavlink build. * Run command 'git submodule init' * Run command 'git submodule update' * To build mavlink, navigate to the "pymavlink" folder and run the command "sudo python setup.py install". ...

If you follow the above instructions word by word then the mavlink folder will be created in the roscopter folder causing the above issue. You actually need to move the mavlink folder to roscopter/src and then compile it. It is strange that the compile did run through fine but resulted in ros setup files being changed, but in any way this seemed to solve it.

The instructions correctly should state: ... * Navigate back to repo folder * Navigate to src folder * Checkout mavlink using submodule (shown below), or create a symlink to an existing mavlink build. ...

It seems there was/is an issue with the roscopter install instructions (h**ps://github.com/epsilonorion/roscopter/wiki):(https://github.com/epsilonorion/roscopter/wiki):

... * Navigate back to repo folder * Checkout mavlink using submodule (shown below), or create a symlink to an existing mavlink build. * Run command 'git submodule init' * Run command 'git submodule update' * To build mavlink, navigate to the "pymavlink" folder and run the command "sudo python setup.py install". ...

If you follow the above instructions word by word then the mavlink folder will be created in the roscopter folder causing the above issue. You actually need to move the mavlink folder to roscopter/src and then compile it. It is strange that the compile did run through fine but resulted in ros setup files being changed, but in any way this seemed to solve it.

The instructions correctly should state: ... * Navigate back to repo folder * Navigate to src folder * Checkout mavlink using submodule (shown below), or create a symlink to an existing mavlink build. ...

It seems there was/is an issue with the roscopter install instructions (https://github.com/epsilonorion/roscopter/wiki):

... * ...

• Navigate back to repo folder * folder
• Checkout mavlink using submodule (shown below), or create a symlink to an existing mavlink build. *
  • Run command 'git submodule init' * init'
  • Run command 'git submodule update' * update'
• To build mavlink, navigate to the "pymavlink" folder and run the command "sudo python setup.py install". install".

...

If you follow the above instructions word by word then the mavlink folder will be created in the roscopter folder causing the above issue. You actually need to move the mavlink folder to roscopter/src and then compile it. It is strange that the compile did run through fine but resulted in ros setup files being changed, but in any way this seemed to solve it.

The instructions correctly should state: ... * state:

...

• Navigate back to repo folder * folder
• Navigate to src folder * folder
• Checkout mavlink using submodule (shown below), or create a symlink to an existing mavlink build. ...
  build.

...