The proposed manifest in the first tutorial is not up-to-date

[AlexanderFabisch]

I tried doing the first tutorial from a plain rock installation (following these instructions)

I get an error when I try to use this autoproj/manifest:

$ amake
  Access method to import data from gitorious.org (git, http or ssh): git
  Access method to import data from github.com (git, http or ssh): git
  Which prepackaged software (a.k.a. 'osdeps') should autoproj install automatically (all, none or a comma-separated list of: os gem pip) ? os,gem,pip

  Which flavor of Rock do you want to use ? stable
  WARN: 
  WARN: The rock.toolchain and rock.base package sets has been moved to github
  WARN: Replace, in autoproj/manifest, the entries for
  WARN: rock-toolchain/package_set and rock-base/package_set by
  WARN: github: rock-core/package_set
  WARN: 
  WARN: if you do not have this line in your manifest, it might be that it is being
  WARN: auto-imported by another package set. Check the imports: section of your
  WARN: remotes' source.yml file
  WARN: osdeps definition for readline, previously defined in .gems/gems/autoproj-1.10.2/lib/autoproj/default.osdeps overridden by autoproj/remotes/orocos.toolchain/orocos.osdeps
  WARN: osdeps definition for boost, previously defined in autoproj/remotes/orocos.toolchain/orocos.osdeps overridden by autoproj/remotes/rock/rock.osdeps
  WARN: osdeps definition for ncurses, previously defined in autoproj/remotes/orocos.toolchain/orocos.osdeps overridden by autoproj/remotes/rock/rock.osdeps
  WARN: osdeps definition for doxygen, previously defined in autoproj/remotes/orocos.toolchain/orocos.osdeps overridden by autoproj/remotes/rock/rock.osdeps
  WARN: osdeps definition for graphviz, previously defined in autoproj/remotes/orocos.toolchain/orocos.osdeps overridden by autoproj/remotes/rock/rock.osdeps
  WARN: osdeps definition for qwt5, previously defined in autoproj/remotes/rock.core/rock.osdeps overridden by autoproj/remotes/rock/rock.osdeps
autoproj: loading ...
run 'autoproj reconfigure' to change configuration options
and use 'autoproj switch-config' to change the remote source for
autoproj's main build configuration
  Do you need compatibility with OCL ? (yes or no): false
Compiling box2d locally, as there is no box2d v2.3.1 Package availible
  the target operating system for Orocos/RTT (gnulinux or xenomai): gnulinux
  which CORBA implementation should the RTT use ? omniorb

autoproj: importing and loading selected packages
  checked out log4cpp         
  checked out ocl         
  checked out stdint_typekit         
autoproj: building and installing packages
  configured CMake for stdint_typekit                                        
  configured CMake for log4cpp                                           
  built log4cpp                                                    
  installed log4cpp                                          
  configured CMake for ocl                                          
  built stdint_typekit                                         
  installed stdint_typekit                              
Build failed                                       
ocl(/home/afabisch/Projekte/rock-tutorials/tools/ocl): failed in build phase
    'make --jobserver-fds=5,6 -j' returned status 2
    see /home/afabisch/Projekte/rock-tutorials/install/log/ocl-build.log for details
    last 10 lines are:

    make[2]: *** [taskbrowser/CMakeFiles/orocos-ocl-taskbrowser.dir/TaskBrowser.cpp.o] Error 1
    make[1]: *** [taskbrowser/CMakeFiles/orocos-ocl-taskbrowser.dir/all] Error 2
    make[1]: *** Waiting for unfinished jobs....
    Linking CXX shared library libprint-gnulinux.so
    [ 21%] Built target print
    Linking CXX shared library liborocos-ocl-helloworld-gnulinux.so
    Linking CXX shared library liborocos-ocl-timer-gnulinux.so
    [ 21%] Built target orocos-ocl-helloworld
    [ 21%] Built target orocos-ocl-timer
    make: *** [all] Error 2

See ocl-build.log for details.

However, the autoproj/manifest that has been provided by the rock installation works for me (at least in this tutorial):

package_sets:
   - github: rock-core/package_set
   - github: rock-core/rock-package_set
   - gitorious: rock-tutorials/package_set
   # Uncomment to enable the Rock/ROS bridge
   # You will also have to uncomment some lines in the layout below
   # - gitorious: rock-ros/package_set

# Layout. Note that the rock.base and orocos.toolchain sets are
# imported by other rock sets.
layout:
   - rock.core
   # Uncomment to enable the Rock/ROS bridge
   # You will also have to uncomment some lines in the package_sets above
   # - rock.ros
   # Uncomment to checkout and build all tutorials  
   # - rock.tutorials    
   - tutorials/message_driver

[doudou]

It seems that your problem is related to OCL handling. You probably enabled it during configuration.

Is it something you actually need ? I do apologize for the bug, orocos-toolchain compatibility is seldom used in Rock and is therefore probably buggy (as you noticed).

[AlexanderFabisch]

I don't know how I activated OCL handling and I most likely did not need it. I just followed the tutorials and it seems like the manifest that is given there seems to be outdated. I just wanted someone to check if that is correct.

[goldhoorn]

You can activate/deactivate ocl during the autoproj configure phase. Even this PR is a bug, you can deactivate ocl by running autoproj reconfigure you should got asked for OCL, type false there and try to use you rock-installation as normal.

[AlexanderFabisch]

Unfortunately I cannot check if it works any more. I have deleted the rock installation that I used for the tutorials already. However, you can see this line in the post:

  Do you need compatibility with OCL ? (yes or no): false

It seems like I actually deactivated OCL!? It seems like the repositories will be cloned anyway with the outdated manifest?

package_sets:
    - gitorious: rock-toolchain/package_set
# Layout. Note that the rock.base, rock.toolchain
# and orocos.toolchain sets are imported
# by other rock sets.
layout:
    - rock.base
    - rock.toolchain
    - tutorials/message_driver

[goldhoorn]

Maybe its a false/yes/no problem. Did you tried no insead of false?

On 24.11.2014 14:21, Alexander Fabisch wrote:

Unfortunately I cannot check if it works any more. I have deleted the rock installation that I used for the tutorials already. However, you can see this line in the post:

Do you need compatibility with OCL ? (yes or no): false

It seems like I actually deactivated OCL!? It seems like the repositories will be cloned anyway with the outdated manifest?

— Reply to this email directly or view it on GitHub https://github.com/rock-core/base-doc/issues/11#issuecomment-64192591.

[AlexanderFabisch]

In my current rock project it works with false. I don't know what happened there.