Problems running tests.

Couldn't get things compiling on Ubuntu 8.10 at all using the provided
install docs (problems with xenomai dependancy), but have managed to get
compiling under cygwin. However I can't run the tests,

Is there something missing from the instructions?? Am I being thick?? The
makefile does not even declare a "make check".... Yet all the
documentation refers to it, both native linux and cygwin docs..

user@winbox ~/orocos-rtt/build
$ make help
The following are some of the valid targets for this Makefile:
... all (the default if no target is provided)
... clean
... depend
... docapi
... docs
... edit_cache
... install
... install/local
... install/strip
... list_install_components
... rebuild_cache
... uninstall
... orocos-rtt-dynamic_gnulinux
... dochtml
... docpdf
... docpng
... message

user@winbox ~/orocos-rtt/build
$ make check
make: *** No rule to make target `check'. Stop.

The information in this e-mail and any attachments transmitted with it are provided in commercial confidence for the intended recipient(s). If you have received this e-mail in error, please notify the Postmaster by e-mail at postmaster [..] .... Any views or opinions expressed are solely those of the author and do not necessarily represent those of DEK.

For local company specific legal information for your country or region and any local contact information for DEK, please refer to:

http://www.dek.com/companyinfo/

This footnote confirms that this message has been checked for the presence of computer viruses and other 'malware' to the best of our knowledge when it left our systems. DEK is not responsible in any way for any malware that may be or become associated with this message. Recipients are strongly urged to use appropriate protection and requested to assure themselves that opening any attachments is safe.

Problems running tests.

On Monday 02 February 2009 17:07:47 markgillespie [..] ... wrote:
> Couldn't get things compiling on Ubuntu 8.10 at all using the provided
> install docs (problems with xenomai dependancy), but have managed to get
> compiling under cygwin. However I can't run the tests,
>
> Is there something missing from the instructions?? Am I being thick?? The
> makefile does not even declare a "make check".... Yet all the
> documentation refers to it, both native linux and cygwin docs..

It's driving me bim-bam. First 'ENABLE_TESTS' was default 'ON', but then users
complained that the cmake aborted with an error that it couldn't find
'cppunit'. So I defaulted it to 'OFF' (which I didn't document 8-]), now
people complain they can't run the unit tests.

Maybe we should always enable the tests but put a warning/error in 'make
check' when cppunit was not installed, such that users get a clue, but those
that don't care aren't bothered.

Peter

Problems running tests.

Are you sure that tests were enabled (run ccmake to see) and that cppunit was found? Without cppunit, it quietly turns the tests off.
S

On Monday, February 02, 2009, at 11:07AM, <markgillespie [..] ...> wrote:
>
>Couldn't get things compiling on Ubuntu 8.10 at all using the provided
>install docs (problems with xenomai dependancy), but have managed to get
>compiling under cygwin. However I can't run the tests,
>
>Is there something missing from the instructions?? Am I being thick?? The
>makefile does not even declare a "make check".... Yet all the
>documentation refers to it, both native linux and cygwin docs..
>
>
>user@winbox ~/orocos-rtt/build
>$ make help
>The following are some of the valid targets for this Makefile:
>... all (the default if no target is provided)
>... clean
>... depend
>... docapi
>... docs
>... edit_cache
>... install
>... install/local
>... install/strip
>... list_install_components
>... rebuild_cache
>... uninstall
>... orocos-rtt-dynamic_gnulinux
>... dochtml
>... docpdf
>... docpng
>... message
>
>user@winbox ~/orocos-rtt/build
>$ make check
>make: *** No rule to make target `check'. Stop.
>
>
>The information in this e-mail and any attachments transmitted with it are provided in commercial confidence for the intended recipient(s). If you have received this e-mail in error, please notify the Postmaster by e-mail at postmaster [..] .... Any views or opinions expressed are solely those of the author and do not necessarily represent those of DEK.
>
>For local company specific legal information for your country or region and any local contact information for DEK, please refer to:
>
>http://www.dek.com/companyinfo/
>
>This footnote confirms that this message has been checked for the presence of computer viruses and other 'malware' to the best of our knowledge when it left our systems. DEK is not responsible in any way for any malware that may be or become associated with this message. Recipients are strongly urged to use appropriate protection and requested to assure themselves that opening any attachments is safe.

Problems running tests.

Tests were off (l had not switched them off, so it seems they default to
off). Perhaps the documentation should mention this... :-)

S Roderick
<kiwi [dot] net [..] ...
> To
markgillespie [..] ...
02/02/2009 16:29 cc
orocos-users [..] ...
Subject
Re: [Orocos-users] Problems running
tests.

Are you sure that tests were enabled (run ccmake to see) and that cppunit
was found? Without cppunit, it quietly turns the tests off.
S

On Monday, February 02, 2009, at 11:07AM, <markgillespie [..] ...> wrote:
>
>Couldn't get things compiling on Ubuntu 8.10 at all using the provided
>install docs (problems with xenomai dependancy), but have managed to get
>compiling under cygwin. However I can't run the tests,
>
>Is there something missing from the instructions?? Am I being thick??
The
>makefile does not even declare a "make check".... Yet all the
>documentation refers to it, both native linux and cygwin docs..
>
>
>user@winbox ~/orocos-rtt/build
>$ make help
>The following are some of the valid targets for this Makefile:
>... all (the default if no target is provided)
>... clean
>... depend
>... docapi
>... docs
>... edit_cache
>... install
>... install/local
>... install/strip
>... list_install_components
>... rebuild_cache
>... uninstall
>... orocos-rtt-dynamic_gnulinux
>... dochtml
>... docpdf
>... docpng
>... message
>
>user@winbox ~/orocos-rtt/build
>$ make check
>make: *** No rule to make target `check'. Stop.
>
>
>The information in this e-mail and any attachments transmitted with it are
provided in commercial confidence for the intended recipient(s). If you
have received this e-mail in error, please notify the Postmaster by e-mail
at postmaster [..] .... Any views or opinions expressed are solely those of
the author and do not necessarily represent those of DEK.
>
>For local company specific legal information for your country or region
and any local contact information for DEK, please refer to:
>
>http://www.dek.com/companyinfo/
>
>This footnote confirms that this message has been checked for the presence
of computer viruses and other 'malware' to the best of our knowledge when
it left our systems. DEK is not responsible in any way for any malware that
may be or become associated with this message. Recipients are strongly
urged to use appropriate protection and requested to assure themselves that
opening any attachments is safe.
>--
>Orocos-Users mailing list
>Orocos-Users [..] ...
>http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
>
>
>

The information in this e-mail and any attachments transmitted with it are provided in commercial confidence for the intended recipient(s). If you have received this e-mail in error, please notify the Postmaster by e-mail at postmaster [..] .... Any views or opinions expressed are solely those of the author and do not necessarily represent those of DEK.

For local company specific legal information for your country or region and any local contact information for DEK, please refer to:

http://www.dek.com/companyinfo/

This footnote confirms that this message has been checked for the presence of computer viruses and other 'malware' to the best of our knowledge when it left our systems. DEK is not responsible in any way for any malware that may be or become associated with this message. Recipients are strongly urged to use appropriate protection and requested to assure themselves that opening any attachments is safe.