-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrating HDE-related repositories in the robotology-superbuild #120
Comments
Probably a new profile may be more clean, especially if in the future more repos are added to it, and also because ideally we also get a mantainer for it. : ) See robotology/robotology-superbuild#142 for draft docs on this. |
Just as a note: the options are necessary on the PC running the producer devices (Windows machine running some |
Hopefully if everything is configured correctly, this could be summarized as "On windows, compile the superbuild with |
As suggested in this issue and #159, I have added HDE to superbuild. The changes are done in the following branch in my repo: As soon as @Yeshasvitvs tests it, to check if it works fine, I will open a PR to robotology/superbuild. The test and PR eventually addresses robotology/robotology-superbuild#205 and robotology/robotology-superbuild#204. |
I test the changes in superbuild using macOS machine, and now we can build the HDE and wearables projects.
Also, currently in order to install successfully, we should manualy change the werables branch to feature/ICub-device-impl. Currently, there is an open PR#25 to metge it to master. |
@kouroshD you can set wearables to master branch. |
It has been set to |
We can procede to test the superbuild in the Virtualizer machine (Windows) or the Monster. |
Please @kouroshD update this issue. |
I have rebased the code on top of master feature/addHDE_rebased and I have added |
Tasks to do:
|
I tested the superbuild with the HDE in Windows machine and I could build it.
Since wearables now is in robotolgy and we are going to add it to superbuild, it is important to have ReadME documentation. Reference: robotology/wearables#14 The dependencies should be updated:
About the USB-CAN2: Also, we need to add following environment variable which is missing:
Also, As I understand "Connect the CAN-USB 2 interface device with the cable to the laptop. Open the Windows Device Manager application and select the unknown device. Select to update the driver and select can_usb2_win64_269 directory. • USB-CAN should now be recognized and it will appear on Windows Device Manager application. Verify if the CAN is correctly identified in the Window Device Manager" this is a runtime dependency not at build/compile time. @Yeshasvitvs , @lrapetti Please update the wiki accordingly as mentioned here, if possible. We need to have a quick check on ubuntu machine, @Yeshasvitvs @diegoferigo @traversaro Can you check it please, since I do not have ubuntu machine. In any case, I open the PR, since it worked in MacOS, it should be very similar for ubuntu as well. |
Just to write down the logics of what is doing in superbuild:
|
I have tested in ubuntu 16.04 . It works as well.
cc @lrapetti @Yeshasvitvs @traversaro @DanielePucci |
PR link: robotology/robotology-superbuild#231 |
@kouroshD we can set the upstream tag to track |
It is not very clean to have another tag instead of |
I believe it’s an acceptable practice (I remember we did something similar with HDE or wearables before) and much better than making an user change it manually. |
For me is fine, I leave this decision to @traversaro , since he is the maintainer of the superbuild. |
We typically do that in https://github.com/robotology/robotology-superbuild/blob/master/cmake/ProjectsTagsMaster.cmake for having a centralized point in which to deal with this info. We did that in the past several times, see:
However, those were specific cases in which a base dependency (in those cases RTF or WB-Toolbox) was updated with a new major version that contained breaking changes (respectively RTF v2 and WB-Toolbox v5), and so we remained for a while on the old stable version waiting for the downstream projects to update to be compatible with the new major versions. Having the superbuild to point to a random-named branch is something that I strongly prefer to avoid unless there are strong reasons to do that. Can you imagine if all the subprojects of the superbuild had this "magic branches"? Unless there is a really strong motivation for this, I would really prefer to avoid pointing to non-stable branches. |
The error that is currently thrown when compiling HumanDynamicEstiamtion in
|
Yes, I have. I will make the changes then. Since you and @Yeshasvitvs are the main maintainers of the repo, I asked you, so that you are aware of changes. |
Great, thanks. I'm fine with that. |
I have updated the wiki page! |
Finally, we have merged the PR. |
To ensure that anyone in the lab that needs to use HDE-related software can use it easily.
We need to understand if it is better to use the Dynamics Profile, or it is better to add a new "profile". If the compilation time increase substantially, it is better to add a new profile.
For previous discussions see https://github.com/dic-iit/component_andy/issues/159
The text was updated successfully, but these errors were encountered: