:-).
--
François Gouget
[EMAIL PROTECTED]
Index: graphics/x11drv/bitmap.c
===
RCS file: /home/wine/wine/graphics/x11drv/bitmap.c,v
retrieving revision 1.34
diff -u -r1.34 bitmap.c
--- graphics/x11drv/bitmap.c2001/09/07 15:28:10 1.34
François Gouget wrote:
[...]
Changelog:
François Gouget [EMAIL PROTECTED]
* console/xterm.c,
[...]
windows/x11drv/clipboard.c
Fix the #include order for config.h
Add #include config.h directives where needed
Fixes the FILE_OFFSET_BITS redefinition warnings on Solaris
output
and make sure it's coherent.
I don't have The Sims... I use a little freeware app that is not available
from the internet anymore, unfortunately :-/.
Do you think you could send this freeware app to me? Would I be able
to run it without too much trouble?
--
François Gouget
[EMAIL
not
changed. Can you try the attached patch?
--
François Gouget
[EMAIL PROTECTED]
Index: graphics/x11drv/dib.c
===
RCS file: /home/wine/wine/graphics/x11drv/dib.c,v
retrieving revision 1.81
diff -u -r1.81 dib.c
--- graphics/x11drv
BI_BITFIELDS which would give the expected 0xff, 0xff00 and
0xff.
What is the value of descr.compression?
--
François Gouget
[EMAIL PROTECTED]
it's coherent.
--
François Gouget
[EMAIL PROTECTED]
#include stdio.h
#include windows.h
//#define VERBOSE
#define CELL_WIDTH 32
#define CELL_HEIGHT 24
typedef struct
{
int bpp;
DWORD rmask;
DWORD gmask;
DWORD bmask;
} dib_format;
static const dib_format dib_formats
tell us if one of these cases is being invoked.
--
François Gouget
[EMAIL PROTECTED]
Roger Fujii wrote:
François Gouget wrote:
You need to first make sure that you are using the GNU toolchain to
build Wine. Otherwise Wine will not work. I believe that not even
./wine will work. Do you have warnings about an unresolved main symbol
when you link Wine's dlls
Roger Fujii wrote:
François Gouget wrote:
well, I had to add an -lc to the gcc -shared to resolve the libc labels
on some of the libraries (winedbg and some others).
I don't think you should not use '-shared' to compile the dlls.
err. double negatives... The choice of gcc
, that works.
I take it that someone does have something that works on solx86?
Yes, a number of applications sort of work, including solitaire.
--
François Gouget
[EMAIL PROTECTED]
François Gouget wrote:
This is a followup on the previous config.h patch, this time tackling
the wine/port.h case.
Hmmm, I see it has been applied to CVS already. But I'm not too happy
with it anymore :-/
I found a problem with 'dlls/winsock/async.c' and
'dlls/winsock/socket.c
Ok, so now that I've got the patch out, there's a weird problem that
I've been having with this piece of code. Apply the following on top of
my previous patch and you'll get the weirdest traces:
--- cut here ---
Index: dlls/comctl32/listview.c
Alexandre Julliard wrote:
Jon Griffiths [EMAIL PROTECTED] writes:
Until we have MS style headers, at least declare msvcrt functions extern "C"
so C++ Winelib programs will link.
I didn't get any feedback to my headers patch. Alexandre, what do I need
to do to get some headers into
Jon Griffiths wrote:
Hi,
Use gcc 2.97 with -fshort-wchar.
Well, this was for VWCL, and I wanted to make the price of entry as low as
possible for the existing win programmers, so I've gone for another solution;
since its a C++ framework its sufficient to use
#define VTEXTW(str)
Jon Griffiths wrote:
Hi,
Of course the name is a bit long (and it's WINE specific) so you
could do:
#define VTEXTW(x) WINE_UNICODE_TEXT(x)
[...]
Actually, having said that, have you tested -fshort-wchar? does it require
libc to be rebuilt? or just to build with a different
While debugging an application it turned out that it was passing a
NULL pointer as the text field in some listview. We were doing a strlen
on it and crashed. See my 'listview fixes' patch on wine-patches.
This got me checking for places where we use a pszText field without
checking for
The questions are about the differences between the two and why
things are done differently. One might be a bug but the other questions
are also so that I can better understand what's going on :-)
(all this is in dlls/comctl32/propsheet.c)
* The most suspicious aspect is the way we
I had written this as a test at a time where it seemed the
application I'm working on needed it. No it looks like it won't need it
after all so it has not been tested.
Is it worth putting in CVS anyway?
I believe CreateMDIWindowW, at least, is correct :-)
--
Franois Gouget
[EMAIL
18 matches
Mail list logo
