GPCS4/3rdParty/pthreads4w/tests
2019-06-23 06:00:43 +08:00
..
common.mk add pthreads4w library 2019-06-23 06:00:43 +08:00
Debug.dsp add pthreads4w library 2019-06-23 06:00:43 +08:00
Debug.dsw add pthreads4w library 2019-06-23 06:00:43 +08:00
Debug.plg add pthreads4w library 2019-06-23 06:00:43 +08:00
Debug.txt add pthreads4w library 2019-06-23 06:00:43 +08:00
Makefile add pthreads4w library 2019-06-23 06:00:43 +08:00
README add pthreads4w library 2019-06-23 06:00:43 +08:00
README.BENCHTESTS add pthreads4w library 2019-06-23 06:00:43 +08:00
runorder.mk add pthreads4w library 2019-06-23 06:00:43 +08:00

Running test cases in this directory
------------------------------------

These make scripts expect to be able to copy the dll, library
and header files from this directory's parent directory,
which should be the pthreads-win32 source directory.

MS VC nmake
-------------

Run the target corresponding to the DLL version being tested:
 
nmake clean VC
 
or:
 
nmake clean VS


GNU GCC make
------------

Run "make clean" and then "make". See the "Known bugs" section
in ..\README.


Writing Test Cases
------------------

Tests written in this test suite should behave in the following manner:

	* If a test fails, leave main() with a result of 1.

	* If a test succeeds, leave main() with a result of 0.

	* No diagnostic output should appear when the test is succeeding
	  unless it is particularly useful to visualise test behaviour.
	  Diagnostic output should be emitted if something in the test
	  fails, to help determine the cause of the test failure. Use assert()
	  for all API calls if possible.

Notes:
------

Many test cases use knowledge of implementation internals which are supposed
to be opaque to portable applications. These should not be used as examples
of methods that can be conformantly applied to application code.