mirror of
https://github.com/reactos/reactos.git
synced 2024-08-02 17:40:58 +00:00
e1ef078741
The idea then would be to have the following behaviour (when specifying the following options in the kernel command line): /DEBUGPORT=COMi --> load KDCOM.DLL and use COMi port (i == 1,2,3,4) if possible. /DEBUGPORT=FOO --> load KDFOO.DLL (useful for KDUSB.DLL, KD1394.DLL, KDBAZIS.DLL for VirtualKD, etc...) /DEBUGPORT=ROSDBG:[COMi|SCREEN|FILE|GDB|...] --> load KDROSDBG.DLL which contains the ROS kernel debugger, and use COMi or SCREEN or... as output port. svn path=/branches/kd++/; revision=58883 |
||
---|---|---|
.. | ||
datalink | ||
include | ||
tcpip | ||
tests | ||
CMakeLists.txt | ||
DIRS | ||
notes.txt | ||
readme.txt | ||
tcpip.rc | ||
tcpip.spec |
Build instructions for TCP/IP protocol driver --------------------------------------------- Building with Visual C++ and Windows NT DDK: Variables: %BASEDIR% = path to NT4 DDK (e.g. c:\ntddk) %DDKBUILDENV% = DDK build environment (free or checked) DDK environment variables must be set! (run setenv.bat) - Create the directory objects/i386/%DDKBUILDENV% - Run "build" to build the driver Building with Mingw32 and ReactOS include files: - Build NDIS.SYS (i.e. "make ndis") - Run "make tcpip" FROM THE ReactOS ROOT DIRECTORY to build the driver