Hey Eric,
My internet connection at home is dead and I do 90% of my development
from there so I cant test/commit changes for a while. Development
on taskmanager in the ReactOS tree has been dead for quite a while
while we work on merging more code from Winehq so change whatever
you guys need and t
Eric Pouech (pouech-eric_at_wanadoo.fr) wrote:
> + Don't depend on msvcrt
> - added wine only dumb macros for _ui64toa and _ultoa
This is not necessary _ui64toa and _ultoa are defined in the ntdll.
See ntdll.spec:
@ cdecl _ui64toa(long long ptr long)
@ cdecl _ultoa(long ptr long)
and ntd
om: Steven Edwards [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 12, 2003 2:38 PM
> To: [EMAIL PROTECTED]; Mike McCormack; Alexandre Julliard
> Cc: Steven Edwards; Eric Pouech; Dimitrie O. Paun;
> [EMAIL PROTECTED]
> Subject: [ros-general] Taskmanger Relicense: Was Unable to
>
Hi Steven,
I'm happy to create a patch to add it into Wine if you get it
relicensed. A task manager would be a nice thing to have in Wine.
Mike
Alexandre Julliard wrote:
Steven Edwards <[EMAIL PROTECTED]> writes:
We have a very nice taskmanger in reactos CVS. It looks and acts just like
Win
ROTECTED]; Mike McCormack; Alexandre Julliard
> > Cc: Steven Edwards; Eric Pouech; Dimitrie O. Paun;
> > [EMAIL PROTECTED]
> > Subject: [ros-general] Taskmanger Relicense: Was Unable to
> > cimpile wineproc
> >
> >
> > Hello All,
> > Would anyone tha
Hello All,
Would anyone that did work on taskmanager be willing to relicense
for use in the Wine Project? It would need to be relicensed as
LGPL or dual licensed LGPL/GPL.
Brian if you see this I dont have your private email. Can someone
forward this if you have the email?
Thanks
Steven
--- Mike
Steven Edwards <[EMAIL PROTECTED]> writes:
> We have a very nice taskmanger in reactos CVS. It looks and acts just like
> Windows taskmanger. It doesnt work under WINE atm because the NtQuery* APIs
> are still buggy but if you wanted to use it and create a bastard step child
> of ReactOS taskmana
On Thu, 11 Sep 2003, Eric Pouech wrote:
> > Well, it makes sense to knowledgeable Linux users, but that's not
> > really our main audience. I was thinking we could find a name that
> > would make it a bit clearer to Windows users what this is about.
> if we take the windows comparison, that would
It could maybe be done with a full dbghelp implementation, but I think
it should also be possible to come up with a specialized interface
just for that need, that should be easier to do. That code is really
too ugly to get in...
one solution would be to store in wineserver the address of a couple o
> likely nothing
> wineproc has been sent before the header overhaul, and hasn't been fixed
> (since Alexandre doesn't seem ready to include wineproc into the CVS tree)
So , what should i do manually to play with wineproc ? system.c is the unique file
that doesn't compile .
Stephan
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> True, but it's internal stuff anyway, we can change it any time
> later on. Maybe we can use this until we have a better implementation
> for toolhelp.dll
It could maybe be done with a full dbghelp implementation, but I think
it should also be poss
Le mar 09/09/2003 à 09:46, BiGgUn a écrit :
> Hi all
>
> When i try to compile wineproc , i got the following error:
> In file included from system.c:3:
> ../../include/psapi.h:25: parse error before "LPVOID"
> ../../include/psapi.h:25: warning: no semicolon at end of struct or union
> (...)
>
On Wed, 9 Sep 2003, Alexandre Julliard wrote:
> Well, I haven't really had time to play with it, but apart from the
> symbol lookup hack it looks good. We really need a better way to
> access the debug channels though.
True, but it's internal stuff anyway, we can change it any time
later on. May
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> On Wed, 10 Sep 2003, Eric Pouech wrote:
>
>> I doubt
>
> What's the problem?
Well, I haven't really had time to play with it, but apart from the
symbol lookup hack it looks good. We really need a better way to
access the debug channels though. Al
On Wed, 10 Sep 2003, Eric Pouech wrote:
> I doubt
What's the problem?
--
Dimi.
Dimitrie O. Paun wrote:
On Wed, 10 Sep 2003, Eric Pouech wrote:
wineproc has been sent before the header overhaul, and hasn't been fixed
(since Alexandre doesn't seem ready to include wineproc into the CVS tree)
Maybe he will if you send in an updated version... :) It'd be nice
to have it in.
On Wed, 10 Sep 2003, Eric Pouech wrote:
> wineproc has been sent before the header overhaul, and hasn't been fixed
> (since Alexandre doesn't seem ready to include wineproc into the CVS tree)
Maybe he will if you send in an updated version... :) It'd be nice
to have it in.
--
Dimi.
BiGgUn wrote:
Hi all
When i try to compile wineproc , i got the following error:
In file included from system.c:3:
../../include/psapi.h:25: parse error before "LPVOID"
../../include/psapi.h:25: warning: no semicolon at end of struct or union
(...)
and many ohter like this.
What did i do in the
Hi all
When i try to compile wineproc , i got the following error:
In file included from system.c:3:
../../include/psapi.h:25: parse error before "LPVOID"
../../include/psapi.h:25: warning: no semicolon at end of struct or union
(...)
and many ohter like this.
What did i do in the wrong way ?
19 matches
Mail list logo
