Ask Your Question
3

Different dependencies depending on ROS version

asked 2011-11-16 00:53:09 -0500

Ugo gravatar image

updated 2014-01-28 17:10:48 -0500

ngrennan gravatar image

Hi all,

I couldn't find a way of checking the ROS version in the manifest.xml: depending on whether we're using electric or older versions, one of my dependencies changes. Do I really have to have 2 branches or is there some trick which would allow me to have one branch, but slight differences depending on the ROS version against which the user compiles?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2011-11-16 01:02:15 -0500

AHornung gravatar image

I was wondering the same some time ago, and came to the conclusion that there was no way around different branches. The next problem will arise in the includes if package names changed between distributions.

edit flag offensive delete link more

Comments

Yes. I wanted to define a flag during compile if it was possible to find out about the ros version. I'll go for separate branches then. Cheers.
Ugo gravatar image Ugo  ( 2011-11-16 01:17:00 -0500 )edit
The includes thing can be fixed. There are #defines for the ROS_VERSION_MAJOR, etc.
dornhege gravatar image dornhege  ( 2011-11-16 01:25:15 -0500 )edit
I, too, would like a solution for manifest.xml and stack.xml version dependencies. As @dornhege said, the includes can use #ifdef.
joq gravatar image joq  ( 2011-11-16 02:38:00 -0500 )edit

How can I get info about what ROS version is being used in my Python code? Can I access the #defines there somewhere?

StFS gravatar image StFS  ( 2012-06-12 06:19:00 -0500 )edit

Version-dependent Python code is worth asking as a separate question.

joq gravatar image joq  ( 2012-06-12 07:09:23 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2011-11-16 00:53:09 -0500

Seen: 151 times

Last updated: Nov 16 '11