[EMAIL PROTECTED] wrote on 03/25/2008 10:21:53
AM:
> On Sat, 2008-03-22 at 13:35 -0400, Renier Morales wrote:
>
> > I noticed that the new plugin has a test directory, but it doesn't
> > contain a Makefile.am file. So you can't run "make test" to run them.
> > Could you see to getting this added? Take a look at the Makefile.am in
> > other test directories for an example.
>
> We will work on this. Also, from IRC, we apparently need to look at
> "make check". Is there a summary of the different make targets, and
> what they should do? If not, I could start that in, perhaps, the main
> README file, or on the wiki. (Some are in the README, but not all.)
No, there is no summary of the different make targets in OpenHPI. Besides
"make test", the rest of the make targets are pretty much the usual you
get with GNU autotools. "make test" comes also from GNU autotools, but its
one of the least known.
check_PROGRAMS is the required automake var you need to specify to make a
directory respond to "make check". autotools then automatically builds and
runs all programs in check_PROGRAMS. A return of 0 means the test PASS,
otherwise it FAILED. It gives you a summary at the end. Its a pretty
useful autools feature.
You can use the TEST_ENVIRONMENT automake var for env setup. A look at the
Makefile.am files in t directories should give you an example. Also, take
a look at the GNU automake manual for documentation -->
http://www.gnu.org/software/automake/#documentation
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
