Hi Gianpaolo

I've pushed a change to the rock's build configuration that should fix
your issue. We are now tracking the toolchain-2.2 branch of ocl and log4cpp.

Hope it will help

Best,
--
Sylvain Joyeux (Dr.Ing.)
Space & Security Robotics

!!! Achtung, neue Telefonnummer!!!

Standort Bremen:
DFKI GmbH
Robotics Innovation Center
Robert-Hooke-Straße 5
28359 Bremen, Germany

Phone: +49 (0)421 178-454136
Fax: +49 (0)421 218-454150
E-Mail: robotik [..] ...

Weitere Informationen: http://www.dfki.de/robotik
-----------------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
(Vorsitzender) Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.: DE 148646973
Steuernummer: 19/673/0060/3
-----------------------------------------------------------------------
--
Orocos-Dev mailing list
Orocos-Dev [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev

On Wednesday 02 February 2011 21:41:54 gprizzi [..] ... wrote:
> Dear Sirs,
>
> from the last week I am trying to get update from rock repository in order
> to rebuild my developing environment.
>
> I issued the commands:
> autoproj update
> autoproj build.
>
> The build command fails building ocl, which I need to use.
> The message error is the following :
>
> building oclBuild failed: ocl: failed in build phase
> 'cmake .' returned status 1
> see /usr/src/rock/install/log/ocl-build.log for details
> last 10 lines are:
>
> Found log4cpp in /usr/src/rock/install/include
> Building component orocos-ocl-common in library
> orocos-ocl-common-gnulinux Building typekit library ocl
> Building plugin library print
> Building plugin library os
> CMake Error at ocl/CMakeLists.txt:13 (orocos_generate_package):
> Unknown CMake command "orocos_generate_package".

This happens when you mix an OCL 'master' with an RTT 'toolchain-2.2' branch.

You need to set your OCL branch to toolchain-2.2 as well.

For the record: in the whole 'orocos-toolchain' directory, each git repository
(project) needs to have the same branch checked out, ie, all on 'master' or
all on 'toolchain-2....'

Peter

Hi,

I know that Rock usually does not use OCL, and OCL build is disabled by
default.

I am wondering whether your error could come from the fact that
(default) Rock builds toolchain-2.2 while the orocos_generate_package
has only been defined in master.

I just say that because I am facing another issue with OCL install from
master regarding this macro (the install log is at my office, so I will
report this error tomorrow morning ;))

Maybe Sylvain and Peter could confirm my first guess.

Charles.

On Wed, 2 Feb 2011 21:41:54 +0100 (CET), gprizzi [..] ... wrote:
> Dear Sirs,
>
> from the last week I am trying to get update from rock repository in
> order to rebuild
> my developing environment.
>
> I issued the commands:
> autoproj update
> autoproj build.
>
> The build command fails building ocl, which I need to use.
> The message error is the following :
>
> building oclBuild failed: ocl: failed in build phase
> 'cmake .' returned status 1
> see /usr/src/rock/install/log/ocl-build.log for details
> last 10 lines are:
>
> Found log4cpp in /usr/src/rock/install/include
> Building component orocos-ocl-common in library
> orocos-ocl-common-gnulinux
> Building typekit library ocl
> Building plugin library print
> Building plugin library os
> CMake Error at ocl/CMakeLists.txt:13 (orocos_generate_package):
> Unknown CMake command "orocos_generate_package".
>
> Here below You can find the complete output of the autoproj update ,
> autoproj build commands.
>
> Am I doing something wrong?
>
> Thank you for your support.
>
> root@UBU1004:/usr/src/rock# autoproj update
> Access method to import data from gitorious.com (git, http or ssh):
> git
> Which flavor of Rock do you want to use ? master
> autodetecting the operating system
> looking for RubyGems updates
> installing/updating RubyGems dependencies: autobuild, autoproj
>
> autoproj and/or autobuild has been updated, restarting autoproj
>
> Access method to import data from gitorious.com (git, http or ssh):
> git
> Which flavor of Rock do you want to use ? master
> Which prepackaged software (a.k.a. 'osdeps') should autoproj install
> automatically (all, ruby, os, none) ? all
> updating autoproj main configuration
> autoproj: updating remote definitions of package sets
> updating rock.toolchain
> updating rock
> rock.toolchain: auto-importing orocos.toolchain
> updating orocos.toolchain
> rock.toolchain: auto-importing rock.base
> updating rock.base
>
> Which flavor of Rock do you want to use ? master
> 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): true
> Which flavor of Rock do you want to use ? master
> 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
> updating base/orogen/types
> updating base/scripts
> updating base/templates/cmake_lib
> updating base/templates/vizkit
> WARN: base/templates/vizkit from rock.base does not have a manifest
> updating base/types
> updating base/types_ruby
> updating control/motor_controller
> updating control/orogen/skid4_control
> updating control/orogen/trajectory_follower
> updating control/orogen/waypoint_navigation
> updating control/trajectory_follower
> updating control/waypoint_navigation
> updating drivers/aggregator
> updating drivers/camera_interface
> updating drivers/canbus
> updating drivers/controldev
> updating drivers/dynamixel
> updating drivers/hokuyo
> updating drivers/iodrivers_base
> updating drivers/mb500
> updating drivers/orogen/canbus
> updating drivers/orogen/controldev
> updating drivers/orogen/dynamixel
> updating drivers/orogen/gps
> updating drivers/orogen/hokuyo
> updating drivers/orogen/parport
> updating drivers/orogen/wifimon
> updating drivers/orogen/xsens_imu
> updating drivers/parport
> updating drivers/xsens_imu
> updating external/libply
> updating external/sisl
> WARN: external/sisl from rock.base does not have a manifest
> updating external/yaml-cpp
> WARN: external/yaml-cpp from rock does not have a manifest
> updating gui/rock_widget_collection
> updating gui/vizkit
> updating image_processing/frame_helper
> updating planning/corridor_navigation
> updating planning/corridor_planner
> updating planning/orogen/corridor_planner
> updating planning/vfh_star
> updating slam/envire
> updating slam/pose_ekf
> updating tools/logger
> updating tools/orocos.rb
> updating tools/pocolog
> updating tools/roby
> updating ocl
> updating orogen
> updating rtt
> updating typelib
> updating utilmm
> updating utilrb
> updating log4cpp
> looking for RubyGems updates
>
> autodetected the shell to be bash, sourcing autoproj shell helpers
> add "Autoproj.shell_helpers = false" in autoproj/init.rb to disable
> autoproj: updated /usr/src/rock/env.sh
> Build finished successfully at Wed Feb 02 21:27:20 +0100 2011
> root@UBU1004:/usr/src/rock# autoproj build
> Access method to import data from gitorious.com (git, http or ssh):
> git
> Which flavor of Rock do you want to use ? master
> autodetecting the operating system
> Which prepackaged software (a.k.a. 'osdeps') should autoproj install
> automatically (all, ruby, os, none) ? all
>
> Which flavor of Rock do you want to use ? master
> 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): true
> Which flavor of Rock do you want to use ? master
> 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
> WARN: base/templates/vizkit from rock.base does not have a manifest
> WARN: external/sisl from rock.base does not have a manifest
> WARN: external/yaml-cpp from rock does not have a manifest
> autoproj: building and installing packages
> building base/types (100%)
> installing base/types
> generating and configuring build system for drivers/hokuyo
> building drivers/hokuyo (100%)
> installing drivers/hokuyo
> generating and configuring build system for gui/vizkit
> building gui/vizkit (100%)
> installing gui/vizkit
> generating and configuring build system for control/motor_controller
> building control/motor_controller (100%)
> installing control/motor_controller
> building oclBuild failed: ocl: failed in build phase
> 'cmake .' returned status 1
> see /usr/src/rock/install/log/ocl-build.log for details
> last 10 lines are:
>
> Found log4cpp in /usr/src/rock/install/include
> Building component orocos-ocl-common in library
> orocos-ocl-common-gnulinux
> Building typekit library ocl
> Building plugin library print
> Building plugin library os
> CMake Error at ocl/CMakeLists.txt:13 (orocos_generate_package):
> Unknown CMake command "orocos_generate_package".
>
> -- Configuring incomplete, errors occurred!
>
> Gianpaolo Rizzi