The way I see it, you decide on a FEATURE freeze. Then you cut the
stable branch. Next, you start stabilizing that branch for release, not
allowing commits into that branch of new features. Once it is released,
you merge the changes there into the development tree, and perform a new
feature
On Fri, Mar 22, 2002 at 06:02:04PM -0500, Steven Edwards wrote:
What's the advantage of this? You'd still have to use the wine kernel
right? I'd loe to be able to get a relay trace from an app
running under
windows, but if you still have to use the wine kernel, there
isn't much
Hi,
I have put up my annotated WineConference 2002 picture collection up on:
http://www.lst.de/~mm/sandiego/pictures.html
Ciao, Marcus
Hello everyone,
I was considering writing a few regression tests for wine,
and after reading Francois' presentation, I thought
perhaps a File I/O would be a good one to implement
(especially since he mentions CreeateFile). So I began
thinking about how to go about it, which led me to the
How do I run a wine perl regression test in Windows?
I thought the entire point was to make it so you don't
need a c-compiler, yet I can't seem to get the tests to
run without the winetest application (which I've been
unable to build on windows so far). Is it planned that
this executable be
Hello All,
I have just been reading the docs on Wine and came across the
--managedAllow the window manager to manage created windows
--winverVersion to imitate
(win95,nt40,win31,nt2k,win98,nt351,win30,win20)
Does the --managed allow my xserver to take care of the windows?
Also,
Hi,
Ive been trying to get Heroes III to work with wine
and I found that it cant load some file it needs
because DOSFS_GetFullPathName
return the path to that file without the backslash at the end
although heroes3 asked for it with a backslash at the end.
it asks for .\\DATA\\ and the method
On 23 Mar 2002, Geoffrey Hausheer wrote:
Hello everyone,
I was considering writing a few regression tests for wine,
and after reading Francois' presentation, I thought
I'm glad my presentation has inspired you :-)
[...]
But I don't see anything in the framework that lets me do
this
On Sun, Mar 24, 2002 at 08:27:41PM +0100, Enrico Horn wrote:
Hi,
Ive been trying to get Heroes III to work with wine
and I found that it cant load some file it needs
because DOSFS_GetFullPathName
return the path to that file without the backslash at the end
although heroes3 asked for it
On 23 Mar 2002, Geoffrey Hausheer wrote:
How do I run a wine perl regression test in Windows?
Well, that's part of the unfinished items. Currently you have to:
* install Perl on Windows
The best seems to be to get Perl from source and compile it, e.g.
with Visual C++.
* get the whole
It's getting harder to fix something without breaking something else :)
In part this is good news as it shows how much is now working, but puts in
to contrast the problem of regression testing especially for this type of
issue. I don't sure that this type of problem can be easily replicated by
InitiallyI thought I'd start with writing a test in Perl,
and I got some basic stuff working. But then I needed to
access structures, constants, etc, and had no idea how to
do this, so I am now rewriting my test in C. My
understanding was that for the most part, the C and Perl
testing
I haven't noticed any access to DR7. The code looks like DR2 should be
written at some point, but I haven't been able to find where. I think it
would help if we could implement an exception handler for DR0..3
read/write accesses which would just store the value somewhere in memory
and
Patrik Stridvall [EMAIL PROTECTED] writes:
* tools/winebuild/build.h,
tools/winebuild/parser.c,
tools/winebuild/relay.c,
tools/winebuild/res16.c,
tools/winebuild/res32.c:
Fixed some more of the issues that prevented
Winebuild from working under Windows.
Why do you need to build
Patrik Stridvall [EMAIL PROTECTED] writes:
* tools/winebuild/build.h,
tools/winebuild/parser.c,
tools/winebuild/relay.c,
tools/winebuild/res16.c,
tools/winebuild/res32.c:
Fixed some more of the issues that prevented
Winebuild from working under Windows.
Why do you need
spec32.c contains the code to build the *.def's from
the .spec.c. This patch fixes this right?
Also when I try to use winebuild to build the *.def
currently under win32, it wont work because its still
trying to look for a *.so instead of a dll when a
import library is listed. The problem is in
On 23 Mar 2002, Geoffrey Hausheer wrote:
InitiallyI thought I'd start with writing a test in Perl,
and I got some basic stuff working. But then I needed to
access structures, constants, etc, and had no idea how to
do this, so I am now rewriting my test in C. My
understanding was that for
17 matches
Mail list logo
