Your mkcvspatch script is pretty sophisticated. It does some things
that genpatch does not. Maybe what would be ideal would be a script
that generates the patch, like genpatch, and another than verifies the
build tree and or resulting patch, like mkcvspatch. The
latter could be
used
Andreas Mohr [EMAIL PROTECTED] wrote:
I seem to remember that it's possible to create combined EXE/ELF
libraries capable of execution on both Linux *and* Windows.
Well, considering that every Windows EXE must start with the 'MZ'
signature, while every ELF executable must start with 'ELF',
"Dimitrie O. Paun" wrote:
Indeed. The problem is that wrc has a semantical preprocessor instead of
a lexical preprocessor.
Why don't we simply use gcc preprocessor?
Because not everybody uses/has gcc to compile wine...
Greetings Bertho
Indeed. The problem is that wrc has a semantical preprocessor instead of
a lexical preprocessor.
Why don't we simply use gcc preprocessor?
Because not everybody uses/has gcc to compile wine...
And a 'standard' cpp would not do? (use autoconf magic: AC_PROG_CPP)
Ciao, Marcus
Why don't we simply use gcc preprocessor?
Because not everybody uses/has gcc to compile wine...
This is certainly NOT a reason:
(1) who is compiling Wine with anything else? Can it be done?
(2) they may not have a Unix OS to run it for. This does not mean that we
include a Unix like OS
Why don't we simply use gcc preprocessor?
Because not everybody uses/has gcc to compile wine...
This is certainly NOT a reason:
(1) who is compiling Wine with anything else? Can it be done?
I do. WineLib works fine with Solaris C.
Wine works for some applications using a gross hack
Patrik Stridvall writes:
It is a little more sensitive than the GNU C preprocessor,
it doesn't like lines ending with "\r\n" for example
but I can fix that it you decide to use it for wrc.
Developpment versions of GCC has to my knowledge some switch to make
them understand "\r\n", however
Hallo,
a compile on a recent CVS tree says:
file.c: In function `ReadFile':
file.c:1180: warning: implicit declaration of function `GetTickCount'
file.c:1152: warning: `starttime' might be used uninitialized in this function
Should files/file.c include winuser.h or prototype it?
Bye
Uwe
On Mon, Mar 20, 2000 at 04:45:25PM +0100, Ulrich Weigand wrote:
Andreas Mohr [EMAIL PROTECTED] wrote:
I seem to remember that it's possible to create combined EXE/ELF
libraries capable of execution on both Linux *and* Windows.
Well, considering that every Windows EXE must start with
Fortunately, standard cpp
seems to be enough, but if we were to require GNU cpp, what
would be the (real) problem???
It is not a real problem but I prefer to minmize the depencies
whenever possible. You have heard the story about
"The straw that broke the {ass,donkey,mule}'s
gerard patel wrote:
At 02:15 PM 3/20/00 -0600, you wrote:
Whatever -- the point is that rewriting and reinvention of the wheel for the
single purpose that it is more convenient to have it included in wine is a
bit silly. We require a C compiler (for now we require gcc with is OK IMO),
[EMAIL PROTECTED] wrote:
[ Sorry for the late reply, I was off-line for two weeks ... ]
Anybody have handy an op-code/postbyte map for x86? I wouldn't mind if
it included segment prefixes too :-). I had an illegal copy of the
original IBM PC spec at one time, and I could sort of
Uwe Bonnes wrote:
Should files/file.c include winuser.h or prototype it?
Actually, GetTickCount (and GetCurrentTime) should reside in
winbase.h, not winuser.h, as GetTickCount is a KERNEL32 routine.
(It used to be a USER routine for 16-bit code ...)
The implementation should probably be
I cannot connect to it nor can I use the cvs repository at all ...
Philippe
Whow, small patch, big discussion!
Sorry for arriving late (the day at the office, time difference,
etc.)
On Mon, 20 Mar 2000, Dimitrie O. Paun wrote:
From: "Bertho Stultiens" [EMAIL PROTECTED]
Indeed. The problem is that wrc has a semantical preprocessor instead of
a
On Mon, 20 Mar 2000, Patrik Stridvall wrote:
[...]
Anyway, I have do some experimentation and I found out that
this simple patch implements a pre wrc call to the C preprocessor.
Works with both Solaris C/CPP and GNU C/CPP.
[...]
Index: wine/tools/wrc/parser.l
[...]
@@ -449,6 +450,14 @@
Lawson Whitney wrote:
Depending on just what the new %cs value is, the lcall instruction can
in fact perform a normal inter-segment call, or else a call via a call
gate, task gate, or to a task state segment.
These gates intel's equivalent of an entry descriptor in GCOS8? :-)
Well, if
On Mon, 20 Mar 2000, Ulrich Weigand wrote:
[EMAIL PROTECTED] wrote:
[ Sorry for the late reply, I was off-line for two weeks ... ]
Depending on just what the new %cs value is, the lcall instruction can
in fact perform a normal inter-segment call, or else a call via a call
gate, task
18 matches
Mail list logo
