Menu
▾
▴
reactos-kernel
|
From: Rex J. <re...@lv...> - 2002-06-01 21:05:54
|
For everyones benefit, I performed the following moves listed below. I sent a message to the list (or I thought I did) a few days ago. But I realized after performing the moves that my alias in my mailer does not point to the right place. So, this is your heads up. You will need to checkout new working areas, as the ones you currently have will have invalid directory paths in them. Sorry for the inconvienence. At 02:02 PM 5/30/02 -0700, you wrote: >Hey Rex > >Ok moving the files on the backend sounds great. Will you have time >to do it this weekend? It shouldn't take too long, if you're just >moving directories, right? Here's what I have: > >In the reactos module: >apps/*: removing apps/test, move apps/system to subsys >everything then left in apps goes to apps/test Done. I moved some of the apps to the utils directory insted of tests dir. I renamed apps/test to apps/tests/test_old. >new directory apps/utils (for utilities like objdir and partinfo) Done. >lib/bzip2: move to services/lib Done. >lib/crtdll: move to win32 module module win32 does not exist. Do you want me to create one? Since the win32 subsystem is an integral part of the kernel, does it make sense to move this to another module? >lib/dflat32: move to rosapps module (?) Done. moved to rosapps/lib/dflat32. >lib/fmifs: move to win32 module >lib/msvcrt: move to win32 module >lib/ole32: move to win32 module >lib/oleaut32: move to win32 module >lib/psapi: move to win32 module >lib/shell32: move to win32 module >lib/version: move to win32 module See above question. >lib/zlib: move to services/lib Done. >lib/ole: move to win32 module >lib/ole32: move to win32 module >lib/rpcrt4: move to win32 module >lib/psapi: move to win32 module (?) see about question. >subsys/os2/*: move to os2 module Done. >subsys/psx/*: move to posix module Done. >move everything currently in services/ to drivers/ >then move rpcss, eventlog to services Done. rpcss and eventlog were not in the services directory however, so I did nothing with them. >Remove everything in the wine module except the makefiles This is best done from cvs proper. I will leave them for now. Rex Jolliff re...@lv... |
|
From: Jason F. <jas...@ya...> - 2002-06-01 22:24:53
|
Thanks Rex!
Unfortunately, when running make I got the following error:
make[1]: Entering directory `C:/ros/reactos/hal/halx86'
gcc -g -o ../../tools/mkconfig ../../tools/mkconfig.c
../../tools/mkconfig ../../include/roscfg.h UP
dlltool --as=as --dllname hal.dll \
--def ./../hal/hal.def \
--output-lib ./hal.a \
--kill-at
make[1]: Leaving directory `C:/ros/reactos/hal/halx86'
make -C services/bus/acpi implib
make: *** services/bus/acpi: No such file or directory. Stop.
make: *** [acpi_implib] Error 2
Is this due to the restructuring?
Thanks
- Jason
--- Rex Jolliff <re...@lv...> wrote:
>
> For everyones benefit, I performed the following moves listed
> below.
> I sent a message to the list (or I thought I did) a few days ago.
> But
> I realized after performing the moves that my alias in my mailer
> does
> not point to the right place. So, this is your heads up. You will
> need to checkout new working areas, as the ones you currently
> have will have invalid directory paths in them. Sorry for the
> inconvienence.
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
|
|
From: Casper H. <ch...@us...> - 2002-06-02 19:23:28
|
s=F8n, 2002-06-02 kl. 00:24 skrev Jason Filby: > Thanks Rex! >=20 > Unfortunately, when running make I got the following error: >=20 > make[1]: Entering directory `C:/ros/reactos/hal/halx86' > gcc -g -o ../../tools/mkconfig ../../tools/mkconfig.c > ../../tools/mkconfig ../../include/roscfg.h UP > dlltool --as=3Das --dllname hal.dll \ > --def ./../hal/hal.def \ > --output-lib ./hal.a \ > --kill-at > make[1]: Leaving directory `C:/ros/reactos/hal/halx86' > make -C services/bus/acpi implib > make: *** services/bus/acpi: No such file or directory. Stop. > make: *** [acpi_implib] Error 2 >=20 > Is this due to the restructuring? >=20 > Thanks > - Jason Should be fixed in CVS now. - Casper |
|
From: Jason F. <jas...@ya...> - 2002-06-01 22:27:39
|
Oh wait, yes we decided that there won't be a win32 module. Everything that says move to win32 module stays in the reactos module. Thanks - Jason --- Rex Jolliff <re...@lv...> wrote: > > For everyones benefit, I performed the following moves listed > below. > I sent a message to the list (or I thought I did) a few days ago. > But > I realized after performing the moves that my alias in my mailer > does > not point to the right place. So, this is your heads up. You will > need to checkout new working areas, as the ones you currently > have will have invalid directory paths in them. Sorry for the > inconvienence. > > At 02:02 PM 5/30/02 -0700, you wrote: > >Hey Rex > > > >Ok moving the files on the backend sounds great. Will you have > time > >to do it this weekend? It shouldn't take too long, if you're just > >moving directories, right? Here's what I have: > > > >In the reactos module: > >apps/*: removing apps/test, move apps/system to subsys > >everything then left in apps goes to apps/test > > Done. I moved some of the apps to the utils directory insted of > tests dir. > I renamed apps/test to apps/tests/test_old. > > >new directory apps/utils (for utilities like objdir and partinfo) > > Done. > > >lib/bzip2: move to services/lib > > Done. > > >lib/crtdll: move to win32 module > > module win32 does not exist. Do you want me to create one? Since > the win32 subsystem is an integral part of the kernel, does it make > sense to move this to another module? > > >lib/dflat32: move to rosapps module (?) > > Done. moved to rosapps/lib/dflat32. > > >lib/fmifs: move to win32 module > >lib/msvcrt: move to win32 module > >lib/ole32: move to win32 module > >lib/oleaut32: move to win32 module > >lib/psapi: move to win32 module > >lib/shell32: move to win32 module > >lib/version: move to win32 module > > See above question. > > >lib/zlib: move to services/lib > > Done. > > >lib/ole: move to win32 module > >lib/ole32: move to win32 module > >lib/rpcrt4: move to win32 module > >lib/psapi: move to win32 module (?) > > see about question. > > >subsys/os2/*: move to os2 module > > Done. > > >subsys/psx/*: move to posix module > > Done. > > >move everything currently in services/ to drivers/ > >then move rpcss, eventlog to services > > Done. rpcss and eventlog were not in the services directory > however, so I did nothing with them. > > >Remove everything in the wine module except the makefiles > > This is best done from cvs proper. I will leave them for now. > > > Rex Jolliff > re...@lv... > > __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
|
From: Steven E. <Ste...@ya...> - 2002-06-01 23:00:48
|
Some of this stuff should stay in the ReactOS module but I though we were going to have a Win32/WINE module? Msvcrt,fmifs,crtdll,advapi,user32,gdi32 is the code we CANNOT use from the WINE tree. These should be blown away and used from the WINE tree. Ole32 Oleaut32 Paspi Shell32 rpcrt4 With the current WINE sources I can build these DLLS out of the Box: comcat.dll comctl32.dll crtdll.dll (unusable for ReactOS as is just a forwarder to msvcrt) crypt32.dll dciman32.dll dinput.dll imagehlp.dll imm32.dll mapi32.dll mpr.dll msdmo.dll msimg32.dll msisys.ocx netapi32.dll odbc32.dll oledlg.dll olepro32.dll rasapi32.dll riched32.dll serialui.dll shdocvw.dll tapi32.dll twain_32.dll (fix those warnings) urlmon winnls.dll winspool.dll wintrust.dll > Oh wait, yes we decided that there won't be a win32 module. > Everything that says move to win32 module stays in the reactos module. > > >lib/fmifs: move to win32 module > > >lib/msvcrt: move to win32 module > > >lib/ole32: move to win32 module > > >lib/oleaut32: move to win32 module > > >lib/psapi: move to win32 module > > >lib/shell32: move to win32 module > > >lib/version: move to win32 module > > >lib/ole: move to win32 module > > >lib/ole32: move to win32 module > > >lib/rpcrt4: move to win32 module > > >lib/psapi: move to win32 module (?) "Every revolution was once a thought in one man's mind" - Ralph Waldo Emerson |
|
From: Casper H. <ch...@us...> - 2002-06-01 23:26:22
|
s=F8n, 2002-06-02 kl. 01:01 skrev Steven Edwards: > Some of this stuff should stay in the ReactOS module but I though we > were going to have a Win32/WINE module?=20 Yes, but maybe we should check if some DLLs need to be merged with the WINE implementation. >=20 > Msvcrt,fmifs,crtdll,advapi,user32,gdi32 is the code we CANNOT use from > the WINE tree.=20 Why can't we use msvcrt and crtdll from WINE? Do the WINE implementations use non-Win32 APIs? - Casper |
|
From: Steven E. <Ste...@ya...> - 2002-06-01 23:45:40
|
> Why can't we use msvcrt and crtdll from WINE? Do the WINE > implementations use non-Win32 APIs? Eric will may need to comment on this one also. From what I had gathered you should not just forward crtdll calls to MSVCRT and that is what the wine crtdll does. I guess it could cause a problem from some applications as crtdll is not supposed to be thread safe and msvcrt is. MSVCRT under wine does you some non-win32 apis and it has a few type conflicts with Mingw. Thanks Steven "Every revolution was once a thought in one man's mind" - Ralph Waldo Emerson |
|
From: Steven E. <Ste...@ya...> - 2002-06-01 22:54:28
|
> >lib/dflat32: move to rosapps module (?) > > Done. moved to rosapps/lib/dflat32. You can blow this away compleately. Rosapps/edit has the same code that actualy works, just not as a dll. I am not interested in trying to work with it at this point. Reactos/apps/tests can also be blown away. These were some tests I ported from WINE and will no longer matter once we have the WINE regression test suite. "Every revolution was once a thought in one man's mind" - Ralph Waldo Emerson |
|
From: KJK::Hyperion <no...@li...> - 2002-06-02 10:25:44
|
At 00.27 02/06/2002, you wrote: >Oh wait, yes we decided that there won't be a win32 module. >Everything that says move to win32 module stays in the reactos module. Win32 will gradually become larger and larger, much bigger than the kernel, possibly the biggest open source project on earth (download the Platform SDK help, or browse the MSDN library to get an idea of the amount of work that needs to be done). With a lot of code that does in no way belong to a kernel. Superfluous code, for people interested just in the kernel (e.g. to create an embedded version, or a completely different operating system based on the same kernel) I vote for a separate module |
|
From: Casper H. <ch...@us...> - 2002-06-02 11:33:15
|
s=F8n, 2002-06-02 kl. 11:59 skrev KJK::Hyperion: > At 00.27 02/06/2002, you wrote: > >Oh wait, yes we decided that there won't be a win32 module. > >Everything that says move to win32 module stays in the reactos module. >=20 > Win32 will gradually become larger and larger, much bigger than the kerne= l,=20 > possibly the biggest open source project on earth (download the Platform=20 > SDK help, or browse the MSDN library to get an idea of the amount of work= =20 > that needs to be done). With a lot of code that does in no way belong to = a=20 > kernel. Superfluous code, for people interested just in the kernel (e.g. = to=20 > create an embedded version, or a completely different operating system=20 > based on the same kernel) >=20 > I vote for a separate module Most of it will be a seperate module when we use WINE instead, but it does not make sense to move them now because then we would have to (re)move them again later. - Casper |
|
From: Robert K. <ro...@ko...> - 2002-06-02 20:46:45
|
So do I. And I prefer to have core win32 components as native or at least in the ROS module. KJK::Hyperion schrieb: > At 00.27 02/06/2002, you wrote: > >Oh wait, yes we decided that there won't be a win32 module. > >Everything that says move to win32 module stays in the reactos module. > > Win32 will gradually become larger and larger, much bigger than the kernel, > possibly the biggest open source project on earth (download the Platform > SDK help, or browse the MSDN library to get an idea of the amount of work > that needs to be done). With a lot of code that does in no way belong to a > kernel. Superfluous code, for people interested just in the kernel (e.g. to > create an embedded version, or a completely different operating system > based on the same kernel) > > I vote for a separate module > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel |
|
From: Aliberti E. <ea...@us...> - 2002-06-02 07:58:12
|
What about a compromise like this one: the win32 module won't be on its own module, but will replace the reactos/subsys subtree in the reactos module? I agreed with David that Win32 and NTOS are related, but I still like having any Win32 piece in a proper subtree and not scattered in the kernel module. On 1 Jun 2002 at 15:27, Jason Filby wrote: > Oh wait, yes we decided that there won't be a win32 module. > Everything that says move to win32 module stays in the reactos > module. > > Thanks > - Jason > > --- Rex Jolliff <re...@lv...> wrote: > > > > For everyones benefit, I performed the following moves listed > > below. > > I sent a message to the list (or I thought I did) a few days ago. > > But I realized after performing the moves that my alias in my mailer > > does not point to the right place. So, this is your heads up. You > > will need to checkout new working areas, as the ones you currently > > have will have invalid directory paths in them. Sorry for the > > inconvienence. > > > > At 02:02 PM 5/30/02 -0700, you wrote: > > >Hey Rex > > > > > >Ok moving the files on the backend sounds great. Will you have > > time > > >to do it this weekend? It shouldn't take too long, if you're just > > >moving directories, right? Here's what I have: > > > > > >In the reactos module: > > >apps/*: removing apps/test, move apps/system to subsys > > >everything then left in apps goes to apps/test > > > > Done. I moved some of the apps to the utils directory insted of > > tests dir. I renamed apps/test to apps/tests/test_old. > > > > >new directory apps/utils (for utilities like objdir and partinfo) > > > > Done. > > > > >lib/bzip2: move to services/lib > > > > Done. > > > > >lib/crtdll: move to win32 module > > > > module win32 does not exist. Do you want me to create one? Since > > the win32 subsystem is an integral part of the kernel, does it make > > sense to move this to another module? > > > > >lib/dflat32: move to rosapps module (?) > > > > Done. moved to rosapps/lib/dflat32. > > > > >lib/fmifs: move to win32 module > > >lib/msvcrt: move to win32 module > > >lib/ole32: move to win32 module > > >lib/oleaut32: move to win32 module > > >lib/psapi: move to win32 module > > >lib/shell32: move to win32 module > > >lib/version: move to win32 module > > > > See above question. > > > > >lib/zlib: move to services/lib > > > > Done. > > > > >lib/ole: move to win32 module > > >lib/ole32: move to win32 module > > >lib/rpcrt4: move to win32 module > > >lib/psapi: move to win32 module (?) > > > > see about question. > > > > >subsys/os2/*: move to os2 module > > > > Done. > > > > >subsys/psx/*: move to posix module > > > > Done. > > > > >move everything currently in services/ to drivers/ > > >then move rpcss, eventlog to services > > > > Done. rpcss and eventlog were not in the services directory > > however, so I did nothing with them. > > > > >Remove everything in the wine module except the makefiles > > > > This is best done from cvs proper. I will leave them for now. > > > > > > Rex Jolliff > > re...@lv... > > > > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! - Official partner of 2002 FIFA World Cup > http://fifaworldcup.yahoo.com > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel |
|
From: Casper H. <ch...@us...> - 2002-06-02 14:05:13
|
s=F8n, 2002-06-02 kl. 09:59 skrev Aliberti Emanuele: > What about a compromise like this one: the win32 module won't be on=20 > its own module, but will replace the reactos/subsys subtree in the=20 > reactos module? I agreed with David that Win32 and NTOS are related,=20 > but I still like having any Win32 piece in a proper subtree and not=20 > scattered in the kernel module. I agree. - Casper >=20 > On 1 Jun 2002 at 15:27, Jason Filby wrote: >=20 > > Oh wait, yes we decided that there won't be a win32 module. > > Everything that says move to win32 module stays in the reactos > > module. > >=20 > > Thanks > > - Jason |
|
From: Casper H. <ch...@us...> - 2002-06-02 19:30:15
|
s=F8n, 2002-06-02 kl. 09:59 skrev Aliberti Emanuele: > What about a compromise like this one: the win32 module won't be on=20 > its own module, but will replace the reactos/subsys subtree in the=20 > reactos module? I agreed with David that Win32 and NTOS are related,=20 > but I still like having any Win32 piece in a proper subtree and not=20 > scattered in the kernel module. I have one more suggestion. Move subsys/win32k to drivers/win32k. It is unique in that it is the only mediator between display drivers and applications. - Casper |
|
From: Jason F. <jas...@ya...> - 2002-06-02 21:58:35
|
Moving win32k.sys to drivers/ sounds good. But can gdi32 and user32 please also stay in the reactos module. The reason is that some subsystem designers may wish to use these for their GUI. Since they are mostly just forwarding calls to win32k, they shouldn't take up too much space. - Jason --- Casper Hornstrup <ch...@us...> wrote: > søn, 2002-06-02 kl. 09:59 skrev Aliberti Emanuele: > > What about a compromise like this one: the win32 module won't be > on > > its own module, but will replace the reactos/subsys subtree in > the > > reactos module? I agreed with David that Win32 and NTOS are > related, > > but I still like having any Win32 piece in a proper subtree and > not > > scattered in the kernel module. > > I have one more suggestion. Move subsys/win32k to drivers/win32k. > It is > unique in that it is the only mediator between display drivers and > applications. > > - Casper > > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- > http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
|
From: Casper H. <ch...@us...> - 2002-06-02 22:23:13
|
s=F8n, 2002-06-02 kl. 23:58 skrev Jason Filby: > Moving win32k.sys to drivers/ sounds good. But can gdi32 and user32 > please also stay in the reactos module. The reason is that some > subsystem designers may wish to use these for their GUI. Since they > are mostly just forwarding calls to win32k, they shouldn't take up > too much space. >=20 > - Jason I think so too - also (as David suggested) that kernel32.dll and advapi32.dll stays in the reactos module. - Casper |
|
From: Robert K. <ro...@ko...> - 2002-06-02 20:52:10
|
> That matches my imagination. - It's a driver! However I want to add an Idea: It would be just consequent to mix gdi32 and user32.dll to win32k.dll which interfaces with .sys. The original gdi32 and user23.dll will then just delegate the calls. I imagine a ...systm%\NATIVE directory. To advapi32 and kernel32.dll: I think they belong more to win32 than to native. > > > I have one more suggestion. Move subsys/win32k to drivers/win32k. It is > unique in that it is the only mediator between display drivers and > applications. > > - Casper > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel |