Robotology
Updating robotology-superbuild installation #621
-
|
Hello, We have some fundamental questions regarding updating our We have here a server (
Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 41 replies
-
|
It's kind of weird that you have all those files modified. Anyway, inspect the relevant CMake variables by launching In particular, You could try to recover from your present situation by doing something like the following: cd /usr/local/src/robot/robotology-superbuild
git restore .
git fetch origin
git checkout v2023.02.3
rm -rf src
cd build
...Or by starting over, cloning the repo anew. ℹ️ At any rate, always refer to the rich documentation available at https://github.com/robotology/robotology-superbuild. cc @traversaro PSI've just noticed that your logs come from 2 repos somehow:
|
Beta Was this translation helpful? Give feedback.
-
|
Many thanks @pattacini . We are going to try a clean install. We'll keep you updated with our progress. |
Beta Was this translation helpful? Give feedback.
-
|
Indeed it strange that you have so many uncommited files. However, the reason you have those is written in the log, i.e. there is a merge ongoing that you can abort with Then whenever you want to revert the new installation, you can just to copy back the directory |
Beta Was this translation helpful? Give feedback.
-
|
Hello @traversaro, thank you for your suggestion. First, we ran "git merge --abort". This was followed by "git pull" which ran with no errors. Then, as indicated in the update instructions, in folder "/usr/local/src/robot/robotology-superbuild/build" we ran " make update-all" which gives the below error. Any ideas about what might cause this? |
Beta Was this translation helpful? Give feedback.
-
|
To clarify, you can create a clean clone and build without touching the other via: If all of this works fine, you just need to open a new terminal to make sure that the Note: never try to source the This should work fine for updating the robotology-superbuild. However, a different verson of the robotology-superbuild on the |
Beta Was this translation helpful? Give feedback.
-
Related to this, the situation apparently is a bit complicated. To help you in the best way, at which version of the robotology-superbuild you want to update? If you just want to update to the latest version, it is the v2023.02.3, see https://github.com/orgs/robotology/discussions/613#discussioncomment-5684218 . |
Beta Was this translation helpful? Give feedback.
-
|
Hi @traversaro . Thanks so much for your thorough answer! Sure, we go with building a new robotology-superbuild. Our aim was to update to the latest version, i.e., v2023.02.3. Based on your answer, I see that we did not enable |
Beta Was this translation helpful? Give feedback.
-
Ok!
To get rid of this error, you need to use the same distro release on all machines that you are using. Each superbuild on its machine is independent, so you need to manually update each one to the same version. The For what regards the update of the firmware, I checked with my colleagues @marcoaccame @pattacini and we found some minor errors in the configuration files of your robot, that we fixed in robotology/robots-configuration#507 . So, in the end the correct steps to update your system are: On all systems, except the icub-head: On the icub-head: Once you did this, you need to manually change the After you installed the updated configuration files, you can proceed to update the firmware. First of all, either clone the https://github.com/robotology/icub-firmware-build repo, or update it if it is already there: At this point, you can update the firmware using the Once everything works, then you can delete the backup directory If you are in doubt on any step, feel free to ask. Unfortunatly the procedure is not obvious, so I may be missing something in my discussion. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @traversaro , thank you very much for such a thorough answer! I could follow your instructions and do all the noted steps with no issue (updating firmware was tricky though). However,
|
Beta Was this translation helpful? Give feedback.
-
|
This is also a screenshot from
|
Beta Was this translation helpful? Give feedback.
-
|
Also, we have a less important issue too. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @paliasgh The log file contains errors referencing the deprecated and thus removed plugin |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
Ok!
To get rid of this error, you need to use the same distro release on all machines that you are using. Each superbuild on its machine is independent, so you nee…