Hello,
[Hope this is the right place for Rock issues. Their website says it is.
If not, advance apologies..]
Today I tried installing Rock, but failed. The system is Debian squeeze
amd64. I followed precisely the instructions at
http://rock-robotics.org/documentation/installation.html
It seems the build fails because it can't find Orocos/CORBA IDL files,
which is weird because I chose 'None' when it asked me which CORBA
implementation RTT should use.
Attached file rock.error contains everything that I saw on the console
(and also what I typed in during the install) and the
orocos.rb-post-install.log is also attached.
I must say that the autoproj system is a bit overwhelming and wonder
what advantages it gives over the (good old?) orocos-1.X method of
download tarball, extract, make build dir, ccmake -i and make. I
eventually need to cross-compile the whole thing to ARM architecture and
wonder how that will work.
Regards,
Sagar
Error installing Rock
On 03/21/2012 04:40 PM, Sagar Behere wrote:
> Hello,
>
> [Hope this is the right place for Rock issues. Their website says it is.
> If not, advance apologies..]
>
> Today I tried installing Rock, but failed. The system is Debian squeeze
> amd64. I followed precisely the instructions at
>
> http://rock-robotics.org/documentation/installation.html
>
> It seems the build fails because it can't find Orocos/CORBA IDL files,
> which is weird because I chose 'None' when it asked me which CORBA
> implementation RTT should use.
Mmmmm ... That's an interesting one. orocos.rb should not be built at
all if CORBA is not present. In general, you won't get much out of the
runtime part of the Rock toolchain without CORBA (we use CORBA to
control the components). I should definitely update the build
configuration to reflect that.
> I must say that the autoproj system is a bit overwhelming and wonder
> what advantages it gives over the (good old?) orocos-1.X method of
> download tarball, extract, make build dir, ccmake -i and make. I
> eventually need to cross-compile the whole thing to ARM architecture and
> wonder how that will work.
A typical rock application (including components, scripts, runtime data)
is 20+ packages, some of them not being C++ based. The maintenance of a
tarball in this case would be a pain. Plus, what would be tarball ? The
toolchain ? The toolchain and all drivers ? ...
Error installing Rock
> Message: 1
> Date: Wed, 21 Mar 2012 16:40:55 +0100
> From: Sagar Behere <sagar [dot] behere [..] ...>
> Subject: [Orocos-users] Error installing Rock
> To: orocos-users [..] ...
> Message-ID: <4F69F687 [dot] 4030205 [..] ...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello,
>
> [Hope this is the right place for Rock issues. Their website says it is.
> If not, advance apologies..]
rock-dev [..] ... would be a better place for rock related questions because not all of the rock user/developer are reading this mailing list.
>
> Today I tried installing Rock, but failed. The system is Debian squeeze
> amd64. I followed precisely the instructions at
>
> http://rock-robotics.org/documentation/installation.html
>
> It seems the build fails because it can't find Orocos/CORBA IDL files,
> which is weird because I chose 'None' when it asked me which CORBA
> implementation RTT should use.
I am afraid this is currently not supported. You have to build with CORBA turned on.
We normally use omniorb but tao should be fine as well.
>
> Attached file rock.error contains everything that I saw on the console
> (and also what I typed in during the install) and the
> orocos.rb-post-install.log is also attached.
>
> I must say that the autoproj system is a bit overwhelming and wonder
> what advantages it gives over the (good old?) orocos-1.X method of
> download tarball, extract, make build dir, ccmake -i and make. I
> eventually need to cross-compile the whole thing to ARM architecture and
> wonder how that will work.
Autoproj gives you create support in building, updating and sharing repositories on a large scale.
I agree that the features are quite overwhelming but the core functionality is quite small.
* autoproj status
autoproj build
autoproj update
There are people at DFKI using as much as possible of autoproj to cross compile rock. If you are interested in this follow the link (http://rock.opendfki.de/wiki/WikiStart/Toolchain/XcompiledRTT)
Regards
Alex
--
Dipl.-Ing. Alexander Duda
Unterwasserrobotik
DFKI Bremen
Robotics Innovation Center
Robert-Hooke-Straße 5
28359 Bremen, Germany
Phone: +49 (0)421 178-456620
Fax: +49 (0)421 178-454150
E-Mail: alexander [dot] duda [..] ...
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
_______________________________________________
Projektleiter-hb mailing list
Projektleiter-hb [..] ...
http://www.dfki.de/mailman/cgi-bin/listinfo/projektleiter-hb
Error installing Rock
On 03/21/2012 05:20 PM, Alexander Duda wrote:
>
>> Message: 1
>> Date: Wed, 21 Mar 2012 16:40:55 +0100
>> From: Sagar Behere<sagar [dot] behere [..] ...>
>> Subject: [Orocos-users] Error installing Rock
>> To: orocos-users [..] ...
>> Message-ID:<4F69F687 [dot] 4030205 [..] ...>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> Hello,
>>
>> [Hope this is the right place for Rock issues. Their website says it is.
>> If not, advance apologies..]
> rock-dev [..] ... would be a better place for rock related questions because not all of the rock user/developer are reading this mailing list.
Maybe we should make sure that they do ;-)
Since we (Rock developers) very soon would like to make publicity for
users that are not developers, I would like to start keeping the dev
list separated from the user list. We agreed with the orocos developers,
a year or so ago, that we could share orocos-users for that since rock
is heavily orocos-based.