This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| icub:yarp_pc104 [2012/11/12 18:24] – ramirezk | icub:yarp_pc104 [2012/11/12 18:25] (current) – [YARP installation on PC104] ramirezk | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== YARP installation on PC104 ====== | ||
| + | Please follow the below steps carefully. | ||
| + | ===== 1) Getting the yarp repositories: | ||
| + | |||
| + | Open a shell on the laptop (icubsrv) | ||
| + | cd / | ||
| + | | ||
| + | And make sure the is not a folder named yarp2, if there is, please move away the folder: | ||
| + | mv yarp2 yarp2.cvs | ||
| + | | ||
| + | Get the yarp source code from the repositories | ||
| + | cd / | ||
| + | svn co https:// | ||
| + | | ||
| + | **IMPORTANT: | ||
| + | |||
| + | ===== 2) Get new startup scripts ===== | ||
| + | |||
| + | |||
| + | Open a shell on the laptop. Get scripts from the local repository: | ||
| + | |||
| + | cp $ICUB_ROOT/ | ||
| + | | ||
| + | ===== 3) Compile the yarp code on the pc104 ===== | ||
| + | |||
| + | On the laptop, open a shell to connect to the pc104 | ||
| + | ssh pc104 | ||
| + | | ||
| + | Now please verify that the following environment variables are present: | ||
| + | |||
| + | YARP_ROOT | ||
| + | YARP_DIR | ||
| + | |||
| + | ICUB_ROOT | ||
| + | ICUB_DIR | ||
| + | |||
| + | You will notice that the variables point to the new repositories. | ||
| + | __**Important: | ||
| + | exists and matches the name of our robot (e.g. iCubMunich01). If not add the following line | ||
| + | in / | ||
| + | | ||
| + | export ICUB_ROBOTNAME=iCubMunich01 | ||
| + | | ||
| + | and boot pc104, so that the new changes are loaded. | ||
| + | |||
| + | ===== 4) Create YARP makefiles ===== | ||
| + | |||
| + | Make sure you are in pc104. Therefore, from the laptop (icubsrv) do: | ||
| + | ssh pc104 | ||
| + | | ||
| + | Create the $YARP_DIR directory (/ | ||
| + | mkdir $YARP_DIR | ||
| + | cd $YARP_DIR | ||
| + | | ||
| + | Clean the cache (This has to be done only when we upgrade the repository): | ||
| + | rm CMakeCache.txt | ||
| + | |||
| + | and generate makefiles | ||
| + | ccmake ../ | ||
| + | | ||
| + | Hit ' | ||
| + | CMAKE_BUILD_TYPE: | ||
| + | CREATE_LIB_MATH, | ||
| + | CREATE_DEVICE_LIBRARY_MODULES: | ||
| + | |||
| + | Configure (hit ' | ||
| + | Now enable: | ||
| + | ENABLE_yarpmod_serial | ||
| + | ENABLE_yarpmod_serialport | ||
| + | ENABLE_yarpmod_portaudio | ||
| + | | ||
| + | Hit ' | ||
| + | |||
| + | ===== 5) Compile YARP ===== | ||
| + | |||
| + | cd $YARP_DIR | ||
| + | make | ||
| + | | ||
| + | __**DO NOT**__ "sudo make install", | ||
| + | |||
| + | ===== 6) Verify the installation: | ||
| + | |||
| + | |||
| + | To verify the procedure type: | ||
| + | |||
| + | yarpdev --list | ||
| + | |||
| + | among the others the list should contains also the new devices: | ||
| + | |||
| + | Device " | ||
| + | Device " | ||
| + | Device " | ||