reactos/rostests/tests/DxHalTest/DxHalTest.rbuild

<module name="dxhaltest" type="win32cui" installbase="bin" installname="dxhaltest.exe">
	<library>user32</library>
	<library>gdi32</library>
	<file>main.c</file>
</module>
1. Remove guithreadinfo from the make file. for it not longer builds. 2. Adding a test apps for starting directdraw hal interface, that I have keep within few ros devs, and one wine devs, it also being using in 2-3 diffent company same code. I known which company that using it with my written premitions I give them on icq or email. But u need a document how to use kernel, d3d, mocomp interface,and some more how to access them. I only show how to start dx hal the interface and using so call IDrawDraw interface. in this apps. svn path=/trunk/; revision=23043 2006-07-13 19:00:05 +00:00			`<module name="dxhaltest" type="win32cui" installbase="bin" installname="dxhaltest.exe">`
fixed follow test, acclertor, alive, alphablend, bitblt, button, button2, capclock, carets, combotst, dibtest, dirdlg, DxHalTest, edit, enhmetafile, enumfonts, enumwnd, enumws, gradient, hello, hivtest, icontest, lineclip, linetest, mdi, midtest svn path=/trunk/; revision=23956 2006-09-07 10:31:37 +00:00			`<library>user32</library>`
1. Remove guithreadinfo from the make file. for it not longer builds. 2. Adding a test apps for starting directdraw hal interface, that I have keep within few ros devs, and one wine devs, it also being using in 2-3 diffent company same code. I known which company that using it with my written premitions I give them on icq or email. But u need a document how to use kernel, d3d, mocomp interface,and some more how to access them. I only show how to start dx hal the interface and using so call IDrawDraw interface. in this apps. svn path=/trunk/; revision=23043 2006-07-13 19:00:05 +00:00			`<library>gdi32</library>`
			`<file>main.c</file>`
			`</module>`