Moving lists to appropriate places sounds good to me too. As for the lib, why would it be better than the current solution?
-----???????? ?????????----- ??: "Timo Kreuzer" timo.kreuzer@web.de ????: "ReactOS Development List" ros-dev@reactos.org ??????????: 31.07.07 11:32 ????: Re: [ros-dev] Winetests
The lib thing is exactly what I had in mind. I just also suggest moving the lists (win32ksvc.db and sysfuncs.lst) from the folder where the nci tool is to the folder where the function implementations are (win32k and ntoskrnl)
The problem is moving thuse file (win32ksvc.db and sysfuncs.lst) is we need rewtite nci tools to found it again. and \ does not works in linux and few other os, the / does not working in windows. and I think it is best have it in nci tools it is easy to found it.
If some does not like the idea create a lib call win32ksyscall.a let me hear it now, I will implement it today night or tomoring other wise, it will be allot easy for our testapps apps and gdi32/user32 using a lib instead a genreated win32k.S for each apps.
----- Original Message ----- From: "Aleksey Bragin" aleksey@reactos.org To: "ReactOS Development List" ros-dev@reactos.org Sent: Tuesday, July 31, 2007 11:46 AM Subject: [ros-dev] ??: Re: Winetests
Moving lists to appropriate places sounds good to me too. As for the lib,
why would it be better than the current solution?
-----???????? ?????????----- ??: "Timo Kreuzer" timo.kreuzer@web.de ????: "ReactOS Development List" ros-dev@reactos.org ??????????: 31.07.07 11:32 ????: Re: [ros-dev] Winetests
The lib thing is exactly what I had in mind. I just also suggest moving the lists (win32ksvc.db and sysfuncs.lst) from the folder where the nci tool is to the folder where the function implementations are (win32k and ntoskrnl)
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
the locations for the lists are stored in the nci makefile
# WIN32K.SYS WIN32K_SVC_DB = $(NCI_BASE_)w32ksvc.db WIN32K_SERVICE_TABLE = subsystems$(SEP)win32$(SEP)win32k$(SEP)include$(SEP)napi.h WIN32K_GDI_STUBS = dll$(SEP)win32$(SEP)gdi32$(SEP)misc$(SEP)$(ARCH)$(SEP)win32k.S WIN32K_USER_STUBS = dll$(SEP)win32$(SEP)user32$(SEP)misc$(SEP)$(ARCH)$(SEP)win32k.S
# NTOSKRNL.EXE KERNEL_SVC_DB = $(NCI_BASE_)sysfuncs.lst KERNEL_SERVICE_TABLE = ntoskrnl$(SEP)include$(SEP)internal$(SEP)napi.h NTDLL_STUBS = dll$(SEP)ntdll$(SEP)$(ARCH)$(SEP)napi.S KERNEL_STUBS = ntoskrnl$(SEP)ex$(SEP)$(ARCH)$(SEP)zw.S
it would be very easy to change this. And there is no need for / or \ (SEP) does the job.
Magnus Olsen schrieb:
The problem is moving thuse file (win32ksvc.db and sysfuncs.lst) is we need rewtite nci tools to found it again. and \ does not works in linux and few other os, the / does not working in windows. and I think it is best have it in nci tools it is easy to found it.