Re: question about standalone tests

2005-05-29 Thread Dimi Paun
On Wed, 2005-05-25 at 09:13 -0700, Dan Kegel wrote: > Now somebody should update > > http://www.winehq.com/site/docs/wine-devel/testing-windows > > with a new section sorta like the following > (Yeah, I should check this text in, but I gotta run. At least I wrote > a first draft, eh?): Thanks f

Re: question about standalone tests

2005-05-25 Thread Dan Kegel
Alexandre Julliard wrote: lzexpand_main.c h:\demo\x\wine\test.h(128) : error C2065: 'stdout' : undeclared identifier ... Adding #include to wine/test.h fixes that first problem, but leaves h:\demo\x\wine\test.h(264) : error C2065: 'winetest_testlist' : undeclared identifier ... I put in som

Re: question about standalone tests

2005-05-25 Thread Alexandre Julliard
Dan Kegel <[EMAIL PROTECTED]> writes: > 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/includ

Re: question about standalone tests

2005-05-25 Thread Dan Kegel
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 bu

Re: question about standalone tests

2005-05-24 Thread Kees Cook
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, it's > supposed to compile with MSVC too. If it doesn't this should be > fixed. There's no reason to add special magic in every test file for > that. Okay, cool. T

Re: question about standalone tests

2005-05-24 Thread Alexandre Julliard
Kees Cook <[EMAIL PROTECTED]> writes: > Hi! My crypt32 protectdata tests were just added to CVS (thanks!) but > they were added without the #ifndef STANDALONE stuff that exists in the > recommended example from the lzexpand test code. The steps here: > http://www.winehq.com/site/docs/wine-deve

Re: question about standalone tests

2005-05-24 Thread Dimitrie Paun
From: "Kees Cook" <[EMAIL PROTECTED]> > Is there some new way to build standalone tests, or should I send a > patch for re-including the #ifndef STANDALONE stuff for the tests? Please don't add the ugly #idfes back. What you need is an out-of-source (dummy) implementation of the Wine test framew

question about standalone tests

2005-05-24 Thread Kees Cook
Hi! My crypt32 protectdata tests were just added to CVS (thanks!) but they were added without the #ifndef STANDALONE stuff that exists in the recommended example from the lzexpand test code. The steps here: http://www.winehq.com/site/docs/wine-devel/testing-windows don't have a method for doing