On Fri, Jun 26, 2009 at 15:59, S Roderick<kiwi [dot] net [..] ...> wrote:
> dpkg-buildpackage works also.
>
> I wonder if svn-buildpackage is pulling the rtt/debian directory from
> trunk using SVN, instead of copying over from the local source? If so,
> then the 1.8 files aren't committed to trunk yet (only 1.4 is there),
> and if it then clears out all versioned install files (ie 1.4) from
> the rtt/debian directory before building, then there will only be the
> template files in build.area/debian. This would cause the problem.
>
> Anyone familiar with how svn-buildpackge works on the inside? Might
> this be the cause?

It's been a while, but I remember that we used aliases to do temporary
builds, such that you didn't need to check in. See the man pages:
" alias svn-b="svn-buildpackage -us -uc -rfakeroot --svn-ignore";
alias svn-br="svn-b --svn-dont-purge --svn-reuse"; alias
svn-bt="svn-buildpackage --svn-tag -rfakeroot";

Those commands have respective meanings: build regardless of new or
changed files; build regardless of new or changed files and reuse the
build directory; build (for upload) and tag."

>
> Peter, how do you normally build the packages?

>From an svn branch with the generated .install/control files checked
in. It was the idea that trunk would contain only the templated files.
>From trunk, you'll need to svn export and generate the control files.

Peter

On Jun 26, 2009, at 04:36 , Leopold Palomo wrote:

> https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=681
>
>
> Leopold Palomo <leo [..] ...> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |leo [..] ...
>
>
>
>
> --- Comment #4 from Leopold Palomo <leo [..] ...> 2009-06-26
> 10:36:12 ---
> Hi,
>
> I normally generate the debian packages for debian stable, now
> Lenny. Rtai
> version doesn't compile:
>
> [ 7%] Building CXX object
> src/CMakeFiles/orocos-rtt-dynamic_lxrt.dir/DataFlowInterface.o
> /srv/src/orocos/rtt/orocos-rtt-1.8.3/src/DataFlowInterface.cpp: In
> member
> function ‘RTT::OperationInterface*
> RTT::DataFlowInterface::createPortObject(const std::string&)’:
> /srv/src/orocos/rtt/orocos-rtt-1.8.3/src/DataFlowInterface.cpp:177:
> error:
> invalid use of incomplete type ‘struct RTT::TaskObject’
> /srv/src/orocos/rtt/orocos-rtt-1.8.3/src/PortInterface.hpp:49:
> error: forward
> declaration of ‘struct RTT::TaskObject’
> /srv/src/orocos/rtt/orocos-rtt-1.8.3/src/DataFlowInterface.cpp:179:
> error:
> invalid use of incomplete type ‘struct RTT::TaskObject’
> /srv/src/orocos/rtt/orocos-rtt-1.8.3/src/PortInterface.hpp:49:
> error: forward
> declaration of ‘struct RTT::TaskObject’
> /srv/src/orocos/rtt/orocos-rtt-1.8.3/src/DataFlowInterface.cpp:181:
> error:
> cannot convert ‘RTT::TaskObject*’ to ‘RTT::OperationInterface*’ in
> return
> make[3]: *** [src/CMakeFiles/orocos-rtt-dynamic_lxrt.dir/
> DataFlowInterface.o]
> Error 1
> make[3]: Leaving directory `/srv/src/orocos/rtt/orocos-rtt-1.8.3/
> build.lxrt'
> make[2]: *** [src/CMakeFiles/orocos-rtt-dynamic_lxrt.dir/all] Error 2
> make[2]: Leaving directory `/srv/src/orocos/rtt/orocos-rtt-1.8.3/
> build.lxrt'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/srv/src/orocos/rtt/orocos-rtt-1.8.3/
> build.lxrt'
> make: *** [build-stamp] Error 2
> dpkg-buildpackage: failure: debian/rules build gave error exit
> status 2
> debuild: fatal error at line 1319:
> dpkg-buildpackage -rfakeroot -D -us -uc failed
> leopold.palomo@quasar:/srv/src/orocos/rtt/orocos-rtt-1.8.3$
>
>
> and I can confirm the S Roderick bug. So, to me the question is if
> it's
> worsewhile to prepare the debian packages for rtt-1.8.x.
>
> Why am I asking this?
>
> Because upstream is preparing rtt2.0 with a reorganization of
> directories and
> files and probably all the stuff for this version won't be usable
> for rtt.
> Also, I don't know if the rtt users use the debian/ubuntu packages,
> so maybe we
> are spending a valuable time in prepare it when the users don't use
> it.

I have customers now who would vastly prefer to install packages, than
build from source. And any mod's we make to the overall framework to
build packages in 1.8, will be just as useful in 2.0. Just the install
file lists will change.

> But, if you think that it's necessary and useful because rtt-2.0
> will be
> release till end of the year, bla, bla ... at the end of July I
> could prepare
> some usable packages for at least xenomai and gnulinux for Lenny and
> unstable.
> (with minimal modifications for ubuntu)

I personally would like to get this working for at least Debian Lenny,
Ubuntu Hardy and Centos 5.
Stephen

On Jun 25, 2009, at 17:26 , S Roderick wrote:

> https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=681
>
>
>
>
>
> --- Comment #3 from S Roderick <kiwi [dot] net [..] ...> 2009-06-25
> 23:26:17 ---
> Created an attachment (id=457)
> --> (https://www.fmtc.be/bugzilla/orocos/attachment.cgi?id=457)
> Modifications from trunk
>
Verified same behaviour on Debian Lenny.