Nothing should change with the resulting binaries (although various #pragma pack directives may have an effect )^:
Clean build tested without problem. Hopefully haven't broken anything with the runtime, ROS still boots ok for me under BOCHS.
Lots of laborious work all to be chucked out once we can finally switch over to the mingw headers full time.
Sorry if this causes anybody�s uncommitted work to be in conflict.
Heaps more coming to an directory near you soon (if nobody objects of course)
I noticed somewhere something like an 'include next' directive, however I can't find it now. In order to save me the research can anybody enlighten me as to its purpose. What I am hoping for is that it tells the pre-proc to go to the next header of the same name in the 'includes' search path. Such a directive would certainly be useful right now!
Regarding the mention on ros-kernel about wine-msvcrt v's ros-msvcrt I was hoping that the mingwacr project would addrs this however it seems to have lost all its steam. Anybody got an update concerning the project?
Somewhat off topic: finally the rains have come -> http://mirror.bom.gov.au/products/IDR032.loop.shtml#image
svn path=/trunk/; revision=6368
1. I removed the global keyboard pointer, and instead acquire a new copy of
the pointer for each thread that needs it. This makes a lock unnecessary,
but is probably less efficient than it could be.
2. Keyboard DLL names are read from the registry in the same way as on win2k.
The (Default) value is taken from HKLM\System\currentcontrolset\nls\locale,
and used to form the key HKLM\System\currentcontrolset\<8-digit-locale>
And get the layout file from the "Layout File" value. I added the entries
for kbdus in hivesys.inf. When others make keyboard layouts, they should be
added here.
svn path=/trunk/; revision=6362
Removed line:
// while (Section != NULL) // RobD - this looks like an error, Section variable never changes inside the while loop...
svn path=/trunk/; revision=6334
initializing to separate function IopInitializeBootDrivers in io/driver.c.
These functions has been renamed:
LdrInitializeBootStartDriver -> IopInitializeBuiltinDriver (moved to io/driver.c)
LdrLoadAutoConfigDrivers -> IopInitializeSystemDrivers
How the driver loading works now:
- The root bus driver is enumerated by IoInit2 and it causes all drivers marked
as boot start to be initialized and attached to respective device tree node.
- Other boot drivers are initialized by IopInitializeBootDrivers (called from
ExpInitializeExecutive).
- After creating system root link (by IoCreateSystemRootLink) the device
tree is travesed by IopInitializePnpServices and all non-boot start drivers
all loaded.
- At last, system start drivers are loaded by IopInitializeSystemDrivers.
svn path=/trunk/; revision=6325
