Bug#833383: ros-std-msgs: split headers and message definitions

2016-08-20 Thread Jochen Sprickerhof
Hi Daniele, * Daniele E. Domenichelli [2016-08-18 19:25]: > Done. Also ros-control-msgs and ros-move-base contain action files, I > moved them as well inside the msgs package. Awesome, thanks a lot! I will start uploading the new versions now. Note that they have to go

Bug#833383: ros-std-msgs: split headers and message definitions

2016-08-18 Thread Daniele E. Domenichelli
Hello Jochen, On 2016-08-16 20:08, Jochen Sprickerhof wrote: /usr/share/sensor_msgs contains srv/ as well. I would propose to put it into the msg package as well. Same hold true for some other packages. Done. Also ros-control-msgs and ros-move-base contain action files, I moved them as well

Bug#833383: ros-std-msgs: split headers and message definitions

2016-08-16 Thread Daniele E. Domenichelli
On 2016-08-11 23:13, Jochen Sprickerhof wrote: But perhaps this is something that should be fixed upstream (i.e. in catkin)? I'm not sure if it is still in development or if it is frozen though, since for ROS2 they are using a different tool. Yes, talking to upstream about it is a good idea

Bug#833383: ros-std-msgs: split headers and message definitions

2016-08-11 Thread Jochen Sprickerhof
* Daniele E. Domenichelli [2016-08-11 18:57]: > Another reason why I would like a cmake config file installed with the > package and not a Findstd_msgs.cmake file in my projects is to be able > to check the version... At some point, perhaps, some message might be > added,

Bug#833383: ros-std-msgs: split headers and message definitions

2016-08-11 Thread Jochen Sprickerhof
* Daniele E. Domenichelli [2016-08-11 11:24]: >cmake_minimum_required(VERSION 2.8.9) >project(foo) > >find_package(YARP REQUIRED) >find_package(std_msgs REQUIRED) > >yarp_generate_bindings(GENERATED_SRCS >

Bug#833383: ros-std-msgs: split headers and message definitions

2016-08-10 Thread Jochen Sprickerhof
Hi Daniele, * Daniele E. Domenichelli [2016-08-10 15:19]: > Thanks! I replied to the comments on github, anyway I'm reporting the > everything here: Great, let's move it all over here. > It would be useful to be able to do something similar anyway, perhaps >

Bug#833383: ros-std-msgs: split headers and message definitions

2016-08-10 Thread Daniele E. Domenichelli
On 2016-08-09 21:29, Jochen Sprickerhof wrote: Hi Daniele, * Daniele E. Domenichelli [2016-08-09 20:03]: I suppose this should be done to all the ros-*-msgs packages, right? Yes :). I already have a patch for ros-std-msgs, you can find it here:

Bug#833383: ros-std-msgs: split headers and message definitions

2016-08-09 Thread Jochen Sprickerhof
Hi Daniele, * Daniele E. Domenichelli [2016-08-09 20:03]: > I suppose this should be done to all the ros-*-msgs packages, right? Yes :). > I already have a patch for ros-std-msgs, you can find it here: > >

Bug#833383: ros-std-msgs: split headers and message definitions

2016-08-09 Thread Daniele E. Domenichelli
Hello Jochen, On 2016-08-05 10:28, Jochen Sprickerhof wrote: So we move everything in /usr/share/std_msgs, right? Package: ros-std-msgs Section: devel Something like that? Sounds good to me. Would you be interested in working on it? Yes, I can work on it. I suppose this should be done

Bug#833383: ros-std-msgs: split headers and message definitions

2016-08-05 Thread Jochen Sprickerhof
* ddomeniche...@drdanz.it [2016-08-05 00:05]: > These messages definition could be used to generate bindings for other > programming languages and/or frameworks. Good point :). > I'd like to have it in a separate package, with a very small number of > dependencies. >

Bug#833383: ros-std-msgs: split headers and message definitions

2016-08-04 Thread ddomenichelli
‎Hello Jochen, > Interesting point, what would be the use case? These messages definition could be used to generate bindings for other programming languages and/or frameworks. In my specific case, in YARP (another middleware for robotics similar to ROS) we have a way to publish/subscribe to

Bug#833383: ros-std-msgs: split headers and message definitions

2016-08-04 Thread Jochen Sprickerhof
Hi Daniele, * Daniele E. Domenichelli [2016-08-03 19:35]: > It would be very useful to be able to install the message definitions without > installing the whole libstd-msgs-dev package that depends on many other > packages. Interesting point, what would be the use case?

Bug#833383: ros-std-msgs: split headers and message definitions

2016-08-03 Thread Daniele E. Domenichelli
Source: ros-std-msgs Severity: wishlist It would be very useful to be able to install the message definitions without installing the whole libstd-msgs-dev package that depends on many other packages. The same applies to all the other ros messages packages. -- System Information: Debian