reactos-kernel

[ros-kernel] Last CVS commit Message + TODO

[Steven E. <ste...@ya...>]

reactos/makefile
/dlls/rpcrt4
/dlls/comctl32
/dlls/shell32
/dlls/ole32
/dlls/winspool
changelog.ros
README_ROS.txt

I will stop flooding the mailing list now as all of
the hard crap is merged. There are still a few small
stubbed dlls I need to merge in this afternoon. For
all purposes we are in sync with the WINE tree as
7-8-02. I dont expect us to do another sync for about
2 months so as to have plenty of time to test and
debug any windowing problems when Jason and David are
ready.

Attached is the TODO + Changelog for the WINE port. We
are now a little better documented as I have also made
some updates to rosdocs. I will be submittied better
more cleaned up documentation to rosdocs, wine and
here as I work on them.

Thanks for dealing with the brokeness of the past few
days.
Steven



__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

Re: [ros-kernel] today's cvs - build errors

[Royce M. I. <ro...@ev...>]

Stupid me... I didn't think to do a make clean. Not used to using makefiles,
yet.

make clean failed, but I was able to fix it by copying RDEL.EXE to the
C:\ReactOS directory.

Should this have been necessary?

Anyways, kicking off the rebuild from post-clean. Hopefully will work this
time :)

Royce3

----- Original Message -----
From: "Steven Edwards" <ste...@ya...>
To: <rea...@li...>
Sent: Monday, July 08, 2002 2:26 AM
Subject: Re: [ros-kernel] today's cvs - build errors


> I always get the warnings about old commands also but
> I jsut did a full rebuild and am not getting the
> problems in ntoskrnl/hal you are seeing. Anyone else
> having this problem?
>
> David can you update and make clean to check and see
> if you get this problem as Royce is? I just did and
> its checking out fine.
>
> Thanks
> Steven
>
> --- Royce Mitchell III <ro...@ev...> wrote:
> > I get a bunch of warnings about old commands...
> >
> > then...
> >
> > ntoskrnl.o(.text+0xb0d8):main.c: undefined reference
> > to `LdrProcessDriver'
> > ntoskrnl.o(.text+0x1efa7):close.c: undefined
> > reference to
>
>
> __________________________________________________
> Do You Yahoo!?
> Sign up for SBC Yahoo! Dial - First Month Free
> http://sbc.yahoo.com
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Oh, it's good to be a geek.
> http://thinkgeek.com/sf
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
> https://lists.sourceforge.net/lists/listinfo/reactos-kernel
>

Re: [ros-kernel] today's cvs - build errors

[Steven E. <ste...@ya...>]

I always get the warnings about old commands also but
I jsut did a full rebuild and am not getting the
problems in ntoskrnl/hal you are seeing. Anyone else
having this problem?

David can you update and make clean to check and see
if you get this problem as Royce is? I just did and
its checking out fine.

Thanks
Steven

--- Royce Mitchell III <ro...@ev...> wrote:
> I get a bunch of warnings about old commands...
> 
> then...
> 
> ntoskrnl.o(.text+0xb0d8):main.c: undefined reference
> to `LdrProcessDriver'
> ntoskrnl.o(.text+0x1efa7):close.c: undefined
> reference to


__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

[ros-kernel] RE: WINE

[Steven E. <ste...@ya...>]

I'm forwarding a copy of this to wine-devel and
reactos-kernel.

The way that I have been doing it is to work out of
the WINE tree to and submit changes back to them. I
try to take a snapshot of the current WINE tree every
few months and that then becomes the -stable branch
for ReactOS. If there is a bug in the ReactOS wine any
patch needs to be wrapped in a #ifdef __REACTOS__ that
way it will be easy for us to submit patches back to
wine. 

The long term goal is to make all of the WINE dlls
upgrade able at anytime. So if you have a idea about a
better way to do it then please let me know. Our
branch is a little odd because it was not tagget right
when they first committed it to CVS. It doesnt really
matter to much about the version numbers though
because we know where changes have been made on the
ReactOS side by the #ifdefs.

Thanks
Steven

--- Jurgen Van Gael
<jur...@st...> wrote:
> Hi Steven,
> 
> I set up my box here in France, and am starting to
> code again. My
> question:
> I am not that experienced with forking etc ... So
> should I modify the
> dll's in the reactos tree and submit patches, diffs
> or new files to
> reactos, or do I submit all my work to WINE?
> 
> Jurgen


__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

Re: [ros-kernel] sorry Steven :-)

[Steven E. <ste...@ya...>]

you will need to make sure cvs is set yo checkout new
directorys. I've added the expand.exe util from wine
to wine/programs

--- David Kredba <kr...@mb...> wrote:
> make -f makefile.ros -C ./../wine/programs/expand
> implib
> make[1]: makefile.ros: No such file or directory
> make[1]: *** No rule to make target `makefile.ros'. 
> Stop.
> make[1]: Entering directory
> `d:/ros/wine/programs/expand'
> make[1]: Leaving directory
> `d:/ros/wine/programs/expand'
> make: *** [expand_implib] Error 2
> 
> David
> 
> 
> 
>
-------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Oh, it's good to be a geek.
> http://thinkgeek.com/sf
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
>
https://lists.sourceforge.net/lists/listinfo/reactos-kernel


__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

[ros-kernel] sorry Steven :-)

[David K. <kr...@mb...>]

make -f makefile.ros -C ./../wine/programs/expand implib
make[1]: makefile.ros: No such file or directory
make[1]: *** No rule to make target `makefile.ros'.  Stop.
make[1]: Entering directory `d:/ros/wine/programs/expand'
make[1]: Leaving directory `d:/ros/wine/programs/expand'
make: *** [expand_implib] Error 2

David

[ros-kernel] today's cvs - build errors

[Royce M. I. <ro...@ev...>]

I get a bunch of warnings about old commands...

then...

ntoskrnl.o(.text+0xb0d8):main.c: undefined reference to `LdrProcessDriver'
ntoskrnl.o(.text+0x1efa7):close.c: undefined reference to
`ObGetReferenceCount'
ntoskrnl.o(.text+0x1f027):close.c: undefined reference to
`ObGetReferenceCount'
ntoskrnl.o(.text+0x2214e):arcname.c: undefined reference to
`xHalQueryDriveLayout'
ntoskrnl.o(.text+0x2e23a):kdebug.c: undefined reference to
`KdPortInitializeEx@12'
ntoskrnl.o(.text+0x2e25a):kdebug.c: undefined reference to
`KdPortInitializeEx@12'
ntoskrnl.o(.text+0x2e30b):kdebug.c: undefined reference to
`KdPortPutByteEx@8'
ntoskrnl.o(.text+0x2e322):kdebug.c: undefined reference to
`KdPortPutByteEx@8'
ntoskrnl.o(.text+0x2e5e6):kdebug.c: undefined reference to
`KdPortPutByteEx@8'
ntoskrnl.o(.text+0x2e605):kdebug.c: undefined reference to
`KdPortGetByteEx@8'
ntoskrnl.o(.text+0x2ffa1):gdbstub.c: undefined reference to
`KdPortGetByteEx@8'

I've attached the entire build output...

[ros-kernel] WINE fork almost done

[Steven E. <ste...@ya...>]

ok I've got everything almost back in sync except
comctl, shell32 and commdlg. there are a few other
things but its mainly stubed dlls. I will do the rest
tonight. I have also fixed the main ReactOS makefile
so you can build what is synced so far without the
system bombing. wine/programs is all up to date but we
will not be able to build and of the GUI programs
untill the wrc/winebuild issues is fixed. Anywat want
to take this? As I said it shouldnt be to hard if you
know the build system well. All we need to do is feed
the Wine resources to WRC and then feed the
resource.res output file to windres as normail. Untill
this is done we will not be able to build most of the
programs or comctl32.dll

I need to sleep for a while. I dont know what is
worse, merging this stuff or playing Civ 3.
Steven

__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

Re: [ros-kernel] Winfile and Winefile

[Steven E. <ste...@ya...>]

THis is nuts, no its 4 not 2. We have 

rosapps/regedit
rosapps/regedt32
rosapps/sysutils/regexpl

and 
wine/programs/regedit

IMHO we should work with WINE on adding a Win32 front
end to the one they have. Currently it is command line
compatible with the windows tool.


--- "KJK::Hyperion" <no...@li...> wrote:
> At 14.43 07/07/2002, you wrote:
> >I am working on and/or have recently modified the
> following modules in 
> >rosapps:
> >rosapps/regedit
> >rosapps/regedt32
> 
> what's the point in keeping two separate registry
> editors? Microsoft has 
> historical reasons, but what about us?


__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

Re: [ros-kernel] Winfile and Winefile

[KJK::Hyperion <no...@li...>]

At 14.43 07/07/2002, you wrote:
>I am working on and/or have recently modified the following modules in 
>rosapps:
>rosapps/regedit
>rosapps/regedt32

what's the point in keeping two separate registry editors? Microsoft has 
historical reasons, but what about us?

Re: [ros-kernel] bugfix

[KJK::Hyperion <no...@li...>]

At 15.19 07/07/2002, you wrote:
> > I would like it if it didnt do a GUI boot by default
> > and you just had to type "win" or something but thats
> > just me.
>I suggest a new kernel command line option '/NOGUI'. Just typing "win" to 
>start the gui won't work because winlogon must always be the first gui app.

"must"? what forces us to?

Re: [ros-kernel] bugfix

[Aliberti E. <ea...@us...>]

On 7 Jul 2002 at 15:19, Eric Kohl wrote:
> I suggest a new kernel command line option '/NOGUI'. Just typing "win"
> to start the gui won't work because winlogon must always be the first
> gui app.

What about getting there by a CSRSS.EXE command line option? That way 
you get a NO/GUI box depending exclusively on the current main 
personality's configuration the ros kernel will load, not on the 
kernel's configuration. 

Re: [ros-kernel] What am I doing wrong? ( was Re: bugfix )

[Eric K. <ek...@rz...>]

"Royce Mitchell III" <ro...@ev...> wrote:


> Okay, I checked, and I have 0.0.0.19, which as far as I can tell is the
> latest kernel.

Could you try the current cvs modules 'reactos' and 'rosapps'?

The 0.0.19 release is older than 130 days and we will release 0.0.20 soon.
The usual time between releases is about 150 days. This means that 0.0.19 is
_outdated_.

Eric

Re: [ros-kernel] bugfix

[Eric K. <ek...@rz...>]

"Steven Edwards" <ste...@ya...> wrote:


> I would like it if it didnt do a GUI boot by default
> and you just had to type "win" or something but thats
> just me.

I suggest a new kernel command line option '/NOGUI'. Just typing "win" to
start the gui won't work because winlogon must always be the first gui app.

Eric

Re: [ros-kernel] Winfile, Winefile and current WINE fork,

[Steven E. <ste...@ya...>]

> Already working with your winefile sources, thanks.
> I hadn't found anything more up to date on the net
> when I recently searched so I just went ahead with
> what was already in our CVS.

Cool.

> I am working on and/or have recently modified the
> following modules in rosapps:
> 
> rosapps/regedit
> rosapps/regedt32
> rosapps/taskmgr
> rosapps/winfile
> 
> Lots of poor quality progress which I can commit
> much more frequently if others are interested in
> keeping tabs.

Well I am interested in sharing the code as much as
possible so we dont duplicate a lot of work. WINE has
adopted our regsrv32 so we can move it out of rosapps
I guess. They also have a regedit that is commandline
compatable with windows regedit. If you are interested
in looking at winefile, regsrv or regedit from the
current wine sources I am going to sync the rest of
wine/programs now.

> Can anybody report on the status of what's currently
> available in terms of comctl32 and DefWndProc(s)
> since I may start knocking the shells out for these
> shortly?

Jason and David have been working on implementing
windowing. I think they are getting very close but
they would have to comment on the DefWndProcs. I think
CreateWindow works now and Jason is working on
adapting the WINE user32 code. As for comctl32 I am
working on fixing the WINEisms in it and shell32. I
will be commiting new snapshots of those today. 

> I usually work with BSD style license so no problem
> from my end. What is the issue and what's required?

There are currently 2 Major forks of Wine, one of
which is X11 and the other at the winehq.com site
which is LGPL. Most people done have a problem doing
X11 but some do and we license each release of ReactOS
as GPL so to contribute back we have to check.

Thanks
Steven

__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

Re: [ros-kernel] Winfile and Winefile

[Robert D. <od...@pn...>]

At 12:07 AM 7/07/2002 -0700, you wrote:
>I noticed there is a new win32 filemanager in rosapps.
>Take a look at wine/programs/winefile and see if you
>find anything useful. The main WineHq source tree
>contains the latest copy and I havent synced then yet.

Already working with your winefile sources, thanks.
I hadn't found anything more up to date on the net
when I recently searched so I just went ahead with
what was already in our CVS.

I am working on and/or have recently modified the
following modules in rosapps:

rosapps/regedit
rosapps/regedt32
rosapps/taskmgr
rosapps/winfile

Lots of poor quality progress which I can commit
much more frequently if others are interested in
keeping tabs.

Can anybody report on the status of what's currently
available in terms of comctl32 and DefWndProc(s)
since I may start knocking the shells out for these
shortly?

>Also if you find somethings that can be adapted to
>Winefile in Winfile can you release the changes as
>LGPL instead of GPL?

I usually work with BSD style license so no problem
from my end. What is the issue and what's required?

Thanks and regards, Robert.

Re: [ros-kernel] CVS commit

[Steven E. <ste...@ya...>]

If you still have problems send me a copy of your
mingw/include/stdlib.h as mine could be hosed also.

Thanks
Steven

--- David Kredba <kr...@mi...> wrote:
> I got this on current cvs tree :

> gcc -I../../include -D__REACTOS__ -D__MINGW__
> -D_WINDOWS -DWINE_NOWINSOCK
> -I../../../reactos/include/wine -I./ -I../../include
> -pipe -march=i386 -c pa
> rser.c -o parser.o
> In file included from ../../include/winbase.h:27,
>                  from parser.c:34:
> ./../include/windef.h:152: warning: `MAX_PATH'


__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

Re: [ros-kernel] Re: no subject & bulding cvs tree

[Steven E. <ste...@ya...>]

I'm still syncing the WINE stuff so for the rest of
the day you will have problems bulding anything in the
WINE fork.

I also have just commited a work around for the
MAX_PATH warning. This is a bug in mingw as MAX_PATH
should not be defined in stdlib.h. I submitted a patch
to them for it but have no idea if it was accepted in
to the -current branch. ReactOS cannot build with the
current Mingw Runtime anyway so it wont matter untill
all of that is fixed. 

Anyway If you do a update now of wine/include/windef.h
the warning should be gone. 

Thanks
Steven

__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

[ros-kernel] Re: no subject & bulding cvs tree

[David K. <kr...@mb...>]

The first error is fixed by Steven.

make -f makefile.ros -C ./../wine/tools/winebuild
make[1]: Entering directory `d:/ros/wine/tools/winebuild'
gcc -I../../include -D__REACTOS__ -D__MINGW__ -D_WINDOWS -DWINE_NOWINSOCK -I
../../../reactos/include/wine -I./ -I../../include -pipe -march=i386 -c im
port.c -o import.o
gcc -I../../include -D__REACTOS__ -D__MINGW__ -D_WINDOWS -DWINE_NOWINSOCK -I
../../../reactos/include/wine -I./ -I../../include -pipe -march=i386 -c ma
in.c -o main.o
gcc -I../../include -D__REACTOS__ -D__MINGW__ -D_WINDOWS -DWINE_NOWINSOCK -I
../../../reactos/include/wine -I./ -I../../include -pipe -march=i386 -c pa
rser.c -o parser.o
In file included from ../../include/winbase.h:27,
                 from parser.c:34:
../../include/windef.h:152: warning: `MAX_PATH' redefined
d:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-7/../../../../include/stdlib.h:62
: warning: this is the location of the previous definition
gcc -I../../include -D__REACTOS__ -D__MINGW__ -D_WINDOWS -DWINE_NOWINSOCK -I
../../../reactos/include/wine -I./ -I../../include -pipe -march=i386 -c re
lay.c -o relay.o
gcc -I../../include -D__REACTOS__ -D__MINGW__ -D_WINDOWS -DWINE_NOWINSOCK -I
../../../reactos/include/wine -I./ -I../../include -pipe -march=i386 -c re
s16.c -o res16.o
In file included from ../../include/winbase.h:27,
                 from res16.c:35:
../../include/windef.h:152: warning: `MAX_PATH' redefined
d:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-7/../../../../include/stdlib.h:62
: warning: this is the location of the previous definition
gcc -I../../include -D__REACTOS__ -D__MINGW__ -D_WINDOWS -DWINE_NOWINSOCK -I
../../../reactos/include/wine -I./ -I../../include -pipe -march=i386 -c re
s32.c -o res32.o
In file included from ../../include/winbase.h:27,
                 from res32.c:35:
../../include/windef.h:152: warning: `MAX_PATH' redefined
d:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-7/../../../../include/stdlib.h:62
: warning: this is the location of the previous definition
gcc -I../../include -D__REACTOS__ -D__MINGW__ -D_WINDOWS -DWINE_NOWINSOCK -I
../../../reactos/include/wine -I./ -I../../include -pipe -march=i386 -c sp
ec16.c -o spec16.o
gcc -I../../include -D__REACTOS__ -D__MINGW__ -D_WINDOWS -DWINE_NOWINSOCK -I
../../../reactos/include/wine -I./ -I../../include -pipe -march=i386 -c sp
ec32.c -o spec32.o
gcc -I../../include -D__REACTOS__ -D__MINGW__ -D_WINDOWS -DWINE_NOWINSOCK -I
../../../reactos/include/wine -I./ -I../../include -pipe -march=i386 -c ut
ils.c -o utils.o
make[1]: *** No rule to make target `../../../reactos/dk/w32/lib/libwine.a',
needed by `winebuild.nostrip.exe'.  Stop.
make[1]: Leaving directory `d:/ros/wine/tools/winebuild'
make: *** [winebuild] Error 2

[ros-kernel] CVS commit

[Steven E. <ste...@ya...>]

syncing more stuff, should be done today.

fixed and compile
dlls/shlwapi
dlls/dplayx

synced parts of
tools/
programs/winefile

__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

Sorry- Re: [ros-kernel] (no subject)

[Steven E. <ste...@ya...>]

Sorry about that. I removed those 2 includes by
mistake when I updated the config.h. I've just added
them back so it should build now.

Steven

--- David Kredba <kr...@mb...> wrote:
> make[1]: Entering directory
> `d:/ros/reactos/lib/ntdll'
> windres --include-dir ../../include --include-dir
> ../../include
> def/ntdll.rc -o def/ntdll.coff
> gcc -g -D__NTDLL__ -I./ -I../../include -pipe
> -march=i386 -c napi.c -o
> napi.o
> gcc -g -D__NTDLL__ -I./ -I../../include -pipe
> -march=i386 -c
> ldr/startup.c -o ldr/startup.o
> gcc -g -D__NTDLL__ -I./ -I../../include -pipe
> -march=i386 -c
> dbg/brkpoint.c -o dbg/brkpoint.o
> gcc -g -D__NTDLL__ -I./ -I../../include -pipe
> -march=i386 -c dbg/debug.c -o
> dbg/debug.o
> gcc -g -D__NTDLL__ -I./ -I../../include -pipe
> -march=i386 -c dbg/print.c -o
> dbg/print.o
> gcc -g -D__NTDLL__ -I./ -I../../include -pipe
> -march=i386 -c
> dbg/winedbg.c -o dbg/winedbg.o
> dbg/winedbg.c:5: wine/debugtools.h: No such file or
> directory
> dbg/winedbg.c:7: warning: parameter names (without
> types) in function
> declaration
> dbg/winedbg.c:7: warning: data definition has no
> type or storage class
> dbg/winedbg.c: In function `get_info':
> dbg/winedbg.c:35: warning: assignment makes pointer
> from integer without a
> cast
> dbg/winedbg.c: At top level:
> dbg/winedbg.c:232: warning: `enum __DEBUG_CLASS'
> declared inside parameter
> list
> dbg/winedbg.c:232: warning: its scope is only this
> definition or
> declaration, which is probably not what you want.
> dbg/winedbg.c:233: parameter `cls' has incomplete
> type
> dbg/winedbg.c: In function `wine_dbg_log':
> dbg/winedbg.c:234: `__DBCL_COUNT' undeclared (first
> use in this function)
> dbg/winedbg.c:234: (Each undeclared identifier is
> reported only once
> dbg/winedbg.c:234: for each function it appears in.)
> dbg/winedbg.c:234: variable `classes' has
> initializer but incomplete type
> dbg/winedbg.c:234: invalid initializer
> dbg/winedbg.c:234: (near initialization for
> `classes')
> dbg/winedbg.c:234: warning: excess elements in
> scalar initializer
> dbg/winedbg.c:234: warning: (near initialization for
> `classes')
> dbg/winedbg.c:234: warning: excess elements in
> scalar initializer
> dbg/winedbg.c:234: warning: (near initialization for
> `classes')
> dbg/winedbg.c:234: warning: excess elements in
> scalar initializer
> dbg/winedbg.c:234: warning: (near initialization for
> `classes')
> dbg/winedbg.c:239: `tid' undeclared (first use in
> this function)
> make[1]: *** [dbg/winedbg.o] Error 1
> make[1]: Leaving directory
> `d:/ros/reactos/lib/ntdll'
> make: *** [ntdll] Error 2


__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

[ros-kernel] (no subject)

[David K. <kr...@mb...>]

make[1]: Entering directory `d:/ros/reactos/lib/ntdll'
windres --include-dir ../../include --include-dir ../../include
def/ntdll.rc -o def/ntdll.coff
gcc -g -D__NTDLL__ -I./ -I../../include -pipe -march=i386 -c napi.c -o
napi.o
gcc -g -D__NTDLL__ -I./ -I../../include -pipe -march=i386 -c
ldr/startup.c -o ldr/startup.o
gcc -g -D__NTDLL__ -I./ -I../../include -pipe -march=i386 -c
dbg/brkpoint.c -o dbg/brkpoint.o
gcc -g -D__NTDLL__ -I./ -I../../include -pipe -march=i386 -c dbg/debug.c -o
dbg/debug.o
gcc -g -D__NTDLL__ -I./ -I../../include -pipe -march=i386 -c dbg/print.c -o
dbg/print.o
gcc -g -D__NTDLL__ -I./ -I../../include -pipe -march=i386 -c
dbg/winedbg.c -o dbg/winedbg.o
dbg/winedbg.c:5: wine/debugtools.h: No such file or directory
dbg/winedbg.c:7: warning: parameter names (without types) in function
declaration
dbg/winedbg.c:7: warning: data definition has no type or storage class
dbg/winedbg.c: In function `get_info':
dbg/winedbg.c:35: warning: assignment makes pointer from integer without a
cast
dbg/winedbg.c: At top level:
dbg/winedbg.c:232: warning: `enum __DEBUG_CLASS' declared inside parameter
list
dbg/winedbg.c:232: warning: its scope is only this definition or
declaration, which is probably not what you want.
dbg/winedbg.c:233: parameter `cls' has incomplete type
dbg/winedbg.c: In function `wine_dbg_log':
dbg/winedbg.c:234: `__DBCL_COUNT' undeclared (first use in this function)
dbg/winedbg.c:234: (Each undeclared identifier is reported only once
dbg/winedbg.c:234: for each function it appears in.)
dbg/winedbg.c:234: variable `classes' has initializer but incomplete type
dbg/winedbg.c:234: invalid initializer
dbg/winedbg.c:234: (near initialization for `classes')
dbg/winedbg.c:234: warning: excess elements in scalar initializer
dbg/winedbg.c:234: warning: (near initialization for `classes')
dbg/winedbg.c:234: warning: excess elements in scalar initializer
dbg/winedbg.c:234: warning: (near initialization for `classes')
dbg/winedbg.c:234: warning: excess elements in scalar initializer
dbg/winedbg.c:234: warning: (near initialization for `classes')
dbg/winedbg.c:239: `tid' undeclared (first use in this function)
make[1]: *** [dbg/winedbg.o] Error 1
make[1]: Leaving directory `d:/ros/reactos/lib/ntdll'
make: *** [ntdll] Error 2

[ros-kernel] building cvs tree

[David K. <kr...@mi...>]

make[1]: Entering directory `d:/ros/reactos/lib/ntdll'
windres --include-dir ../../include --include-dir ../../include def/ntdll.rc -o def/ntdll.coff
gcc -g -D__NTDLL__ -I./ -I../../include -pipe -march=i386 -c napi.c -o napi.o
gcc -g -D__NTDLL__ -I./ -I../../include -pipe -march=i386 -c ldr/startup.c -o ldr/startup.o
gcc -g -D__NTDLL__ -I./ -I../../include -pipe -march=i386 -c dbg/brkpoint.c -o dbg/brkpoint.o
gcc -g -D__NTDLL__ -I./ -I../../include -pipe -march=i386 -c dbg/debug.c -o dbg/debug.o
gcc -g -D__NTDLL__ -I./ -I../../include -pipe -march=i386 -c dbg/print.c -o dbg/print.o
gcc -g -D__NTDLL__ -I./ -I../../include -pipe -march=i386 -c dbg/winedbg.c -o dbg/winedbg.o
dbg/winedbg.c:5: wine/debugtools.h: No such file or directory
dbg/winedbg.c:7: warning: parameter names (without types) in function declaration
dbg/winedbg.c:7: warning: data definition has no type or storage class
dbg/winedbg.c: In function `get_info':
dbg/winedbg.c:35: warning: assignment makes pointer from integer without a cast
dbg/winedbg.c: At top level:
dbg/winedbg.c:232: warning: `enum __DEBUG_CLASS' declared inside parameter list
dbg/winedbg.c:232: warning: its scope is only this definition or declaration, which is probably not what you want.
dbg/winedbg.c:233: parameter `cls' has incomplete type
dbg/winedbg.c: In function `wine_dbg_log':
dbg/winedbg.c:234: `__DBCL_COUNT' undeclared (first use in this function)
dbg/winedbg.c:234: (Each undeclared identifier is reported only once
dbg/winedbg.c:234: for each function it appears in.)
dbg/winedbg.c:234: variable `classes' has initializer but incomplete type
dbg/winedbg.c:234: invalid initializer
dbg/winedbg.c:234: (near initialization for `classes')
dbg/winedbg.c:234: warning: excess elements in scalar initializer
dbg/winedbg.c:234: warning: (near initialization for `classes')
dbg/winedbg.c:234: warning: excess elements in scalar initializer
dbg/winedbg.c:234: warning: (near initialization for `classes')
dbg/winedbg.c:234: warning: excess elements in scalar initializer
dbg/winedbg.c:234: warning: (near initialization for `classes')
dbg/winedbg.c:239: `tid' undeclared (first use in this function)
make[1]: *** [dbg/winedbg.o] Error 1
make[1]: Leaving directory `d:/ros/reactos/lib/ntdll'
make: *** [ntdll] Error 2

David

Re: [ros-kernel] implementation question

[Steven E. <ste...@ya...>]

I would assume it may have something to do with the
line right above that

"This function is retained for backward compatibility
with Windows 3.1. Use ExpandEnvironmentStrings
instead. "

Win3.1 wasnt the most stable beast M$ has ever made
and I assume the "unexpected" could cause very bad
results in other areas besides the target application.

--- Royce Mitchell III <ro...@ev...> wrote:
> I was reading about shell32.DoEnvironmentSubst(),
> and I came across an
> interesting comment in MS documentation:
> 
> Parameters must contain valid values that are not
> NULL. You are responsibile
> for validating these values. If you do not validate
> it, you will experience
> unexpected results.
> 
> Here's the link where that comment can be found:
> 
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/pla
>
tform/shell/reference/functions/doenvironmentsubst.asp
> 
> Now, my question is this: what is the harm in
> checking for invalid params,
> and returning failure instead of just letting the OS
> do it's "unexpected"
> thing?
> 
> Royce3
> 
> 
> 
> 
>
-------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Got root? We do.
> http://thinkgeek.com/sf
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
>
https://lists.sourceforge.net/lists/listinfo/reactos-kernel


__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

[ros-kernel] Winfile and Winefile

[Steven E. <ste...@ya...>]

I noticed there is a new win32 filemanager in rosapps.
Take a look at wine/programs/winefile and see if you
find anything useful. The main WineHq source tree
contains the latest copy and I havent synced then yet.

Also if you find somethings that can be adapted to
Winefile in Winfile can you release the changes as
LGPL instead of GPL?

Thanks
Steven

__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com