<feed xmlns='http://www.w3.org/2005/Atom'>
<title>liblitmus.git/tests/runner.c, branch 2012.1</title>
<subtitle>[ARCHIVE] The userspace library for LITMUS^RT 2010. Now on GitHub.</subtitle>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/liblitmus.git/'/>
<entry>
<title>refactor: switch back from SCons to make</title>
<updated>2010-11-09T21:35:32+00:00</updated>
<author>
<name>Bjoern B. Brandenburg</name>
<email>bbb@cs.unc.edu</email>
</author>
<published>2010-11-06T18:34:18+00:00</published>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/liblitmus.git/commit/?id=35b88760be5b5dbda859f4697702efc0b3cd2663'/>
<id>35b88760be5b5dbda859f4697702efc0b3cd2663</id>
<content type='text'>
We originally switched from make to scons because
1) our makefiles were not very good;
2) SCons promised to make maintaining the build system simpler.

Unfortunately, SCons has become more and more difficult to deal with
as we moved to supporting several architecture and cross compilation,
to the extend that we ended up re-creating make functionality in SCons.

So let's switch back to make using a "clean" Makefile.

Thanks a lot to Andrea Bastoni and Chris Kenna for feedback on
previous iterations of these patches.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We originally switched from make to scons because
1) our makefiles were not very good;
2) SCons promised to make maintaining the build system simpler.

Unfortunately, SCons has become more and more difficult to deal with
as we moved to supporting several architecture and cross compilation,
to the extend that we ended up re-creating make functionality in SCons.

So let's switch back to make using a "clean" Makefile.

Thanks a lot to Andrea Bastoni and Chris Kenna for feedback on
previous iterations of these patches.
</pre>
</div>
</content>
</entry>
<entry>
<title>Introduce test framework for LITMUS^RT.</title>
<updated>2010-02-21T02:48:29+00:00</updated>
<author>
<name>Bjoern B. Brandenburg</name>
<email>bbb@cs.unc.edu</email>
</author>
<published>2010-02-21T02:48:29+00:00</published>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/liblitmus.git/commit/?id=f3d21c128e5b40acd1f15e3ddcd7fd54ca3a9bed'/>
<id>f3d21c128e5b40acd1f15e3ddcd7fd54ca3a9bed</id>
<content type='text'>
This is the beginning of the LITMUS^RT testsuite.
The main design goals are flexibility and ease of test writing.

To create a new test, simply write a test case in any C file in the
tests/ subdirectory. The buildsystem will find the test and hook it
up with the testrunner.

Have a look at tests/fdso.c and include/tests.h to get an idea for what
tests look like.

Tests can be executed with the 'runtests' tool. Each testcase is executed
in a separate process in order to ensure that tests do not influence
each other.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This is the beginning of the LITMUS^RT testsuite.
The main design goals are flexibility and ease of test writing.

To create a new test, simply write a test case in any C file in the
tests/ subdirectory. The buildsystem will find the test and hook it
up with the testrunner.

Have a look at tests/fdso.c and include/tests.h to get an idea for what
tests look like.

Tests can be executed with the 'runtests' tool. Each testcase is executed
in a separate process in order to ensure that tests do not influence
each other.
</pre>
</div>
</content>
</entry>
</feed>
