CBFalconer wrote:
Frank Heckenbach wrote:
CBFalconer wrote:
... snip ...
- The test suite could well be separated into a separate
tarball, and made available separately. This would not preclude including that tarball in the source distribution. I gather that the full source is totally unnecessary for test execution.
No problem. We're going to migrate the whole GPC stuff to a new server soon, setting up some automated package building etc., and we can probably do this in one go. If you'd like to have such a tarball now, just let me know.
I would. The djgpp source zip includes a large tarball for the GPC sources, and the test suite is contained therein.
I hope you can handle tar.gz files. In this case, they're quite a bit smaller (230 KB vs. 650 KB) since zip compresses on a file level which is quite ineffecient for large numbers of small files (like here). If not, let me know ...
ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/gpc-test-20011015.tar.gz
Please note that it already contains some tests for the latest GPC changes which haven't been uploaded yet, so these tests will fail on your version. (I'll be making some more changes before uploading them as a whole.)
If you separate it please describe clearly what directory it is to be untarred in.
Doesn't matter. Just put it in any directory and run make (or, under DJGPP under Windoze, dostest.bat, to avoid some system limit). `make clean' afterwards should remove all files generated during the test run and leave only the original files.
You can also run the tests in another directory by doing make -sf </path/to/testsuite/>Makefile srcdir=/path/to/testsuite
Let me get the existing stuff working and I will see if I can find time and energy to re-organize it. Have you run it all under DJGPP?
Yes. I routinely let it run under DJGPP (within Linux Dosemu, though this shouldn't make a big difference).
It would be nice if the ready to roll tarball was packed up under the DJGPP system, so the first step is to unzip in the DJGPP home directory, and then untar the test stuff from whereever it appears. Less opportunity for silly errors that way.
I'm not too familiar with the DJGPP file system hierarchy, so perhaps someone can tell me how to do it (which directory etc.). I should then probably also create a manifest file (which I haven't done yet). For now, just put it in any directory and remove the whole directory when you want to get rid of it. I'm leaving the `p/test' prefix in the archive, so it won't clobber the directory in which you extract it.
Is there any documentation about what the tests are supposed to be testing - I looked at one or two, and it was far from clear.
Sorry, there isn't (except in a few cases where noted in program comments or obvious from the file name or something).
Frank