Closed S-Dafarra closed 3 years ago
I think it would be convenient to have the same text in the help message also in the README of the directory of github, but then we have two places with the same info duplicated, so feel free to choose the solution that you prefer.
NOTE: I had to switch the compilation to static by default in order to use the ReadOnlyControlBoard plugin without installing. I am not sure if I am missing something.
Yes, that is totally correct, and I am also happy that the support for having yarp devices as static libraries still works fine, this is quite convenient for embedded scenario and that could be useful to have also on BlockFactory or other similar libraries.
NOTE: I had to switch the compilation to static by default in order to use the ReadOnlyControlBoard plugin without installing. I am not sure if I am missing something.
Yes, that is totally correct, and I am also happy that the support for having yarp devices as static libraries still works fine, this is quite convenient for embedded scenario and that could be useful to have also on BlockFactory or other similar libraries.
To clarify, it would also possible to just specify that YARP plugins or the ReadOnlyControlBoard
in particular are compiled as static, but as we don't have other libraries I think that is ok for this project.
NOTE: I had to switch the compilation to static by default in order to use the ReadOnlyControlBoard plugin without installing. I am not sure if I am missing something.
Yes, that is totally correct, and I am also happy that the support for having yarp devices as static libraries still works fine, this is quite convenient for embedded scenario and that could be useful to have also on BlockFactory or other similar libraries.
To clarify, it would also possible to just specify that YARP plugins or the
ReadOnlyControlBoard
in particular are compiled as static, but as we don't have other libraries I think that is ok for this project.
I wanted to do that, but I did not understand how to do it from the yarp
macros.
I think it would be convenient to have the same text in the help message also in the README of the directory of github, but then we have two places with the same info duplicated, so feel free to choose the solution that you prefer.
Does it make sense to only document the --help
option?
We quickly discussed F2F, and we concluded the following:
I wanted to do that, but I did not understand how to do it from the
yarp
macros.
Apparently, this is currently not possible.
Does it make sense to only document the --help option?
According to the case, it might be easier to have the documentation online. Nevertheless, having duplicate information is not good. So I will stick to documenting the --help
option only for the time being.
I have added a basic README. Let me know if you are ok with merging.
I have added a basic README. Let me know if you are ok with merging.
For me, it's ok.
Thanks! Do you prefer Merge or Squash and Merge?
Thanks! Do you prefer Merge or Squash and Merge?
As you prefer. Also Squash and Merge works
In the end, the modifications needed were a lot, but I tested it on the robot and seems to be working fine. The most difficult part has been defining a proper syntax. I hope it is well explained when typing
--help
. I also added thedefault
keyword that should work when connecting to a known robot (onlyicub
oricubSim
for the time being). I have tested it on iCubGenova09 and with iCubGazeboV3, and iCubGazeboV2_5.NOTE: I had to switch the compilation to static by default in order to use the
ReadOnlyControlBoard
plugin without installing. I am not sure if I am missing something.Closes https://github.com/robotology/idyntree-yarp-tools/issues/6