reactos/drivers/directx/dxg/dxg.rbuild

<?xml version="1.0"?>
<!DOCTYPE module SYSTEM "../../../tools/rbuild/project.dtd">
<module name="dxg" type="kernelmodedriver" installbase="system32/drivers" installname="dxg.sys">
	<importlibrary definition="dxg.spec" />
	<include base="dxg">.</include>
	<include base="dxg">include</include>
	<library>dxgthk</library>
	<library>ntoskrnl</library>
	<file>main.c</file>
	<file>ddhmg.c</file>
	<file>eng.c</file>
	<file>historic.c</file>
	<file>dxg.rc</file>
</module>
start adding dxg.sys svn path=/branches/reactx/; revision=29761 2007-10-21 23:38:13 +00:00			`<?xml version="1.0"?>`
XML Compliance Patch for the RBUILD Files. By Samuel Serapion svn path=/trunk/; revision=45631 2010-02-20 12:41:24 +00:00			`<!DOCTYPE module SYSTEM "../../../tools/rbuild/project.dtd">`
- Fix dxg's includes. svn path=/trunk/; revision=32421 2008-02-19 17:18:18 +00:00			`<module name="dxg" type="kernelmodedriver" installbase="system32/drivers" installname="dxg.sys">`
modified tools/rbuild/backend/mingw/modulehandler.cpp modified tools/rbuild/backend/mingw/modulehandler.h modified tools/rbuild/module.cpp Split rules for .spec files as input files vs import libraries. .spec files can now be specified independently as <file>s (to generate and compile a .stubs.c file) and <importlibrary> (to generate and compile a .spec.def file) .spec files are now specified in <importlibrary>s directly (instead of pointing to the non-existing, generated .spec.def file. Whose idea was that? sounds like the doing of Arch Blackmann) Allow multiple modules to share a single .spec file without using <importlibrary base="..."> Allow static libraries to use .spec files in <importlibrary> Emit comments in makefile.auto so rules can be traced back to the code that generated them deleted lib/debugsup/debugsup-ntos.def added lib/debugsup/debugsup-ntos.spec modified lib/debugsup/debugsup.rbuild .def -> .spec <<hundreds of rbuild files>> Remove <file> entry for spec file if there are no stubs to compile .spec.def -> .spec in <importlibrary> entries Soon: making all keyboard layouts use a single .spec file Dedicated to: Samuel Serapión, Stefan Ginsberg, and all the fellow team members who'll have an aneurysm at this commit See issue #3746 for more details. svn path=/trunk/; revision=36870 2008-10-21 13:51:49 +00:00			`<importlibrary definition="dxg.spec" />`
Adding code from 2004, DxDdStartupDxGraphics, DxDdCleanupDxGraphics(), DdHmgDestroy() svn path=/branches/reactx/; revision=29780 2007-10-22 16:26:59 +00:00			`<include base="dxg">.</include>`
- Fix dxg's includes. svn path=/trunk/; revision=32421 2008-02-19 17:18:18 +00:00			`<include base="dxg">include</include>`
actvate more code and slash away more notes to the trachcan, and smaller cleanup svn path=/branches/reactx/; revision=29798 2007-10-22 21:15:10 +00:00			`<library>dxgthk</library>`
add complete startup process code for dxg.sys svn path=/branches/reactx/; revision=29848 2007-10-24 11:05:44 +00:00			`<library>ntoskrnl</library>`
start adding dxg.sys svn path=/branches/reactx/; revision=29761 2007-10-21 23:38:13 +00:00			`<file>main.c</file>`
Add : struct _DD_BASEOBJECT base on alex and own and jim informations Add : struct _DD_ENTRY base on alex info change : gpentDdHmgr and gpentDdHmgrLast to PDD_ENTRY pointer change : move all DdHmg releated api to own file Implement : DdHmgLock not yet use Implement : VerifyObjectOwner it verify how own the DD_ENTRY svn path=/trunk/; revision=31505 2007-12-30 21:14:20 +00:00			`<file>ddhmg.c</file>`
add complete startup process code for dxg.sys svn path=/branches/reactx/; revision=29848 2007-10-24 11:05:44 +00:00			`<file>eng.c</file>`
Add documentations for EngDxIoctl, NtGdiDxgGenericThunk optimize for EngDxIoctl, NtGdiDxgGenericThunk implement DxDxgGenericThunk, DxDdIoctl for they are outdated, they are left for compatible issue. svn path=/branches/reactx/; revision=29847 2007-10-24 08:13:39 +00:00			`<file>historic.c</file>`
start adding dxg.sys svn path=/branches/reactx/; revision=29761 2007-10-21 23:38:13 +00:00			`<file>dxg.rc</file>`
			`</module>`
No results found.