question about standalone tests
Dan Kegel
dank at kegel.com
Wed May 25 04:30:53 CDT 2005
The STANDALONE stuff is my creation; apologies to anyone
offended by it. It does fill a real need, but belongs
in wine/test.h, not in each test, I agree. I was being lazy.
Now, on to Alexandre's claim:
On Tue, May 24, 2005 at 05:24:11PM +0200, Alexandre Julliard wrote:
> You should be able to build by simply copying over wine/test.h
Tried that.
$ wget -O lzexpand_main.c 'http://cvs.winehq.org/cvsweb/~checkout~/wine/dlls/lzexpand/tests/lzexpand_main.c?rev=1.4&content-type=text/plain'
$ mkdir wine
$ wget -O wine/test.h 'http://cvs.winehq.org/cvsweb/~checkout~/wine/include/wine/test.h?rev=1.14'
$ cl -I. -DWINETEST_WANT_MAIN -D_X86_ lzexpand_main.c
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for 80x86
Copyright (C) Microsoft Corporation 1984-2002. All rights reserved.
lzexpand_main.c
h:\demo\x\wine\test.h(128) : error C2065: 'stdout' : undeclared identifier
...
Adding #include <stdio.h> to wine/test.h fixes that first problem, but leaves
h:\demo\x\wine\test.h(264) : error C2065: 'winetest_testlist' : undeclared identifier
...
So including wine/test.h isn't enough at the moment.
Maybe there needs to be a
#ifdef STANDALONE
...
#endif
section in wine/test.h that defines winetest_testlist, etc.
I just looked, and it's probably easy to do, but somewhat
beyond what I want to do at 2 in the morning.
(Besides, I'm not supposed to be typing, my wrists are sore.)
- Dan
--
Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
More information about the wine-devel
mailing list