Re: [LTP] Regarding LTP Devel Package

[Randy D. <rd...@xe...>]

On Wed, 20 Feb 2008 17:48:46 +0530 Subrata Modak wrote:

> > Hi,
> > 
> > background:
> > 
> > LTP's library (lib/tst_res.c) supports a common test results output
> > format.  LTP also provides tools/apicmds/ltpapicmd.c as a command-line
> > interface to the test results library code.
> > 
> > I want to use some common test results format in some automated
> > kernel testing that I am doing (just plain text, not XML :).
> > I could make up a(nother) test results format, but why do that?
> > or I could choose something else that is already out there.
> > Anyway, I'm testing using the LTP API command-line tools with
> > non-LTP tests, so I have made a small tarball of lib/tst_res.c,
> > tools/apicmds/ltpapicmd.c, 2 .h files, and a new Makefile so that
> > these can be built and installed for other users of them.
> > 
> > The .c and .h files are used without modifications.  Here is the
> > Notes file from the tarball:
> > 
> > ---
> > ltp-tstres-001:  20071231
> > Provides LTP standard common output test results command-line tools
> > that can be used by other testing projects so that all can share a
> > common test results output format.
> > 
> > Taken from ltp-full-20071130 (unmodified):
> > 	tools/apicmds/ltpapicmd.c
> > 	lib/tst_res.c
> > 	include/test.h
> > 	include/usctest.h
> > 
> > + (new) Makefile, which builds binary 'ltp_tst_res' & will install it
> > (using "make install") into DESTDIR=/usr/local/bin and make symlinks for
> > the (8) LTP tst_xyz command-line tools.  "make uninstall" removes the
> > installed files.
> > ---
> 
> Randy,
> 
> Recently there has been some requirement of an LTP-DEVEL Package (may
> also be in the form of an RPM) which will contain runltp, pan, lib and
> other LTP tools, for facilitating development of unit test cases by
> developers, who may not be interested to download the entire LTP bundle
> to start developing their interested test cases.
> 
> To begin with we can have some RPM which on installation will:
> 
> 1) build either liltp.a or libltp.so and install it under /lib
> or /usr/lib,
> 2) build tool/apicmds and install the binary version(s) of tst_res,
> tst_resm, tst_brk, etc (to be used by Shell Script Test Cases) either
> at /usr/bin/ or /bin directory,
> 3) Builds as well as installs pan under /usr/bin/ or /bin directory,
> [Presently pan is called with absoulte path inside runltp:
> ${LTPROOT}/pan/pan],
> 4) Installs ustest.h file under /include or /usr/include,
> 5) And can even install runltp script under /usr/bin/ or /bin.
> 
> With this, user can develop Unit Test Cases anywhere in the system and
> then:
> 1) While building test cases, LTP headers and Library definitions can be
> statically or dynamically linked,
> 2) While running, runltp can invoke pan as it is in system path [/bin
> or /usr/bin]
> 3) Script test cases which uses the binary versions of apicmds can also
> be run, as, these apicmds are in system path.
> 
> If this can be developed and used successfully, later we can think of
> bisecting LTP tree to 2 parts namely devel-package and
> testcases-package.
> 
> What is you idea on this ??

Hi Subrata,

It all sounds good to me.

I would think that most of the target directories would be
parameter(s) to the build of ltp-devel-package.

Thanks.

> Regards--
> Subrata
> 
> https://sourceforge.net/tracker/index.php?func=detail&aid=1888999&group_id=3382&atid=103382,
> https://sourceforge.net/tracker/index.php?func=detail&aid=1888996&group_id=3382&atid=103382,
> https://sourceforge.net/tracker/index.php?func=detail&aid=1888979&group_id=3382&atid=103382,
> 
> > 
> > The tarball for release 001 is available at:
> > http://oss.oracle.com/~rdunlap/ltp-tstres/ltp-tstres-001.tar.gz
> > (this may not be a permanent location)

---
~Randy