Chico3/Archive: Difference between revisions
Jump to navigation
Jump to search
(initial version of archive page) |
|||
Line 2: | Line 2: | ||
== Additional RobotCub software == | == Additional RobotCub software == | ||
=== iCub: downloading the repository === | === iCub: downloading the repository === |
Revision as of 15:11, 21 July 2010
Obsolete installation
Additional RobotCub software
iCub: downloading the repository
In /home/icub, do:
cvs -d vislab@cvs.robotcub.org:/cvsroot/robotcub co iCub
For now, don't compile iCub but start installing YARP instead. (This is the most general approach which always works. However, since this machine does not have special iCub hardware to be found by YARP, like in the case of the PC104, then in this case we could've probably compiled straight ahead.)
YARP
- Type this from the homedir (/home/icub):
mkdir ~/YARP cd ~/YARP cvs -d:pserver:anonymous@yarp0.cvs.sourceforge.net:/cvsroot/yarp0 login cvs -z3 -d:pserver:anonymous@yarp0.cvs.sourceforge.net:/cvsroot/yarp0 co -P yarp2 cd yarp2
- (SKIP THIS POINT, AS THIS MACHINE IS NOT ATTACHED TO dragonfly esdMotionControl headcalibrator xsensmtx) Enter yarp2/conf and do:
cp ExternalModules.cmake.template ExternalModules.cmake
then write the following lines in ExternalModules.cmake:
SET(EXTERNAL_MODULES icub) SET(icub_DIR "/home/icub/iCub/src/modules")
- Proceed with the configuration and compilation:
ccmake .
Click 'c' when CMake starts, then enable:
COMPILE_NEW_YARPVIEW <-- right? CREATE_DEVICE_LIBRARY_MODULES CREATE_GUIS CREATE_LIB_MATH
Click 'c' again, then choose
ENABLE_yarpmod_opencv_grabber
Click 'c' a couple of times more, until nothing happens when you do it. Now hit 'g': generate and quit.
make make test sudo make install
iCub: compiling and installing
- Off we go:
cd /home/icub/iCub ccmake . c <-- whenever necessary
- Enable these modules:
BUILD_IN_ROOT CREATE_GUIS_GTK CREATE_GUIS_GTKMM CREATE_GUIS_QT
- And finally:
g make sudo make install