Hi,
i was checking out the changelog of OCL and noticed the following
commit:
r28909 | psoetens | 2008-02-05 10:52:36 +0100 (Tue, 05 Feb 2008) | 1 line
Cleanup debian packaging directory, minor dependency fixes and added
README.PACKAGING.
------------------------------------------------------------------------
Since i still haven't found a good way to build my own orocos-rtt
debian packages ( amd64 system without rtai or xenomai, so only
gnulinux packages) I checked out the README.PACKAGING to see if there
was anything interesting in there. I noticed the folowing:
You can edit this script and set different Orocos targets. The
default is "gnulinux lxrt xenomai".
[\quote]
I was wondering if the same would be possible for RTT, so i could
build packages for only gnulinux without having to change the source.
Ruben
RTT debian packages
On Thursday 07 February 2008 09:42:50 Ruben Smits wrote:
>
> Since i still haven't found a good way to build my own orocos-rtt
> debian packages ( amd64 system without rtai or xenomai, so only
> gnulinux packages) I checked out the README.PACKAGING to see if there
> was anything interesting in there. I noticed the folowing:
>
>
> You can edit this script and set different Orocos targets. The
> default is "gnulinux lxrt xenomai".
> [\quote]
>
> I was wondering if the same would be possible for RTT, so i could
> build packages for only gnulinux without having to change the source.
This does not imply that it does not build for one of these OS's, it just
implies that they are not *packaged*. The rules file is not adapted by this
script and hence, builds for all targets. Also the control.in file lists
build dependencies for all targets.
As I understand it, both RTAI 3.6 and Xenomai 2.4 are available for amd64, so
what is the exact problem ? I'm willing to help port RTT & OCL to amd64, but
I thought Leo had already tested this and running (to a certain extent).
Peter