Yes! It made my original, simple command work.
I hope this makes it into CVS soon.
On 10/2/05, Dimi Paun <[EMAIL PROTECTED]> wrote:
> On Sun, 2005-10-02 at 22:19 -0700, Dan Kegel wrote:
> > I'd love that. It should sense _X86_ and set __i386__ if
> > found, too.
>
> Does this work?
>
> Index: in
On Sun, 2005-10-02 at 22:19 -0700, Dan Kegel wrote:
> I'd love that. It should sense _X86_ and set __i386__ if
> found, too.
Does this work?
Index: include/windef.h
===
RCS file: /var/cvs/wine/include/windef.h,v
retrieving revision
On 10/2/05, Dimi Paun <[EMAIL PROTECTED]> wrote:
> > You need one more define: -Dinline=__inline
>
> This is non-obvious. Can't we detect MSVC (say in windef.h)
> and define inline and the other defines that we need?
I'd love that. It should sense _X86_ and set __i386__ if
found, too.
On Mon, 2005-10-03 at 09:29 +0900, Dmitry Timoshkov wrote:
> You need one more define: -Dinline=__inline
This is non-obvious. Can't we detect MSVC (say in windef.h)
and define inline and the other defines that we need?
It seems rather silly to have to specify them on the command line.
--
Dimi P
On 10/2/05, Dmitry Timoshkov <[EMAIL PROTECTED]> wrote:
>> cl -DSTANDALONE -D_X86_ -D__i386__ -I../../../include file.c
> > ../../../include\winbase.h(2271) : error C2054: expected '(' to follow
> > 'inline'
> >
> You need one more define: -Dinline=__inline
Ah. Thanks. (I haven't tried it yet,
"Dan Kegel" <[EMAIL PROTECTED]> wrote:
> ../../../include\winbase.h(2271) : error C2054: expected '(' to follow
> 'inline'
>
> Evidently cl doesn't like the inline functions in winnt.h and winbase.h.
>
> Any suggestions? It seems a bit strange to be using wine's winnt.h
> when I have MS's head
On Sun, 2005-10-02 at 10:08 -0700, Dan Kegel wrote:
> D'oh. No, it's not quite that simple to build standalone with cl;
> you have to avoid using wine's headers
That doesn't seem right -- AFAIK, it should work with the Wine headers.
--
Dimi Paun <[EMAIL PROTECTED]>
Lattica, Inc.
On 10/2/05, Dan Kegel <[EMAIL PROTECTED]> wrote:
> To compile a test standalone, one should be able to do e.g.
> cd dlls/msvcrt/tests
> cl -DSTANDALONE -D_X86_ -I../../../include file.c
D'oh. No, it's not quite that simple to build standalone with cl;
you have to avoid using wine's headers, l
While looking at
http://bugs.winehq.org/show_bug.cgi?id=1899
I noticed that dlls/msvcrt/tests/file.c didn't test
O_APPEND, so I thought I'd try building that
test standalone, running it under Windows,
and adding the missing test logic.
(Rather than building under Windows, I used
a shell script tha