You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've successfully built OpenRV on CentOS 7 but I had to perform some extra steps that were not mentioned in the instructions (OpenRV/docs/build_system/config_linux_centos7.md):
it's necessary to install the ninja build system as well as meson: sudo yum install ninja-build meson
at some point, the build failed with an error and upon inspection of the file name that was mentioned, I've noticed the shebang for tcsh at the beginning. I was able to complete the build after installing tcsh using sudo yum install tcsh
I have also experienced a weird Qt-related issue and I couldn't figure out the source of it. I had installed Qt 5.15.2 in its default location (~/Qt). rvcmds.sh detected this as QT_HOME, but rvbootstrap failed early on because it couldn't copy Qt resources and translations from /opt/Qt/5.15.2/
I don't know cmake enough to figure out where that path came from, and I had installed Qt into that custom location in /opt at some point in the past. Maybe something was still cached somewhere and it's not a problem that can occur for other people. In my case I was able to work around this by simply adding a symlink from ~/Qt to /opt/Qt.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've successfully built OpenRV on CentOS 7 but I had to perform some extra steps that were not mentioned in the instructions (OpenRV/docs/build_system/config_linux_centos7.md):
sudo yum install ninja-build meson
sudo yum install tcsh
I have also experienced a weird Qt-related issue and I couldn't figure out the source of it. I had installed Qt 5.15.2 in its default location (~/Qt). rvcmds.sh detected this as QT_HOME, but rvbootstrap failed early on because it couldn't copy Qt resources and translations from /opt/Qt/5.15.2/
I don't know cmake enough to figure out where that path came from, and I had installed Qt into that custom location in /opt at some point in the past. Maybe something was still cached somewhere and it's not a problem that can occur for other people. In my case I was able to work around this by simply adding a symlink from ~/Qt to /opt/Qt.
Beta Was this translation helpful? Give feedback.
All reactions