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 the build with the free-of-charge windows CLI compiler (which the "STANDALONE" stuff works fine with).
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?
From: "Kees Cook" kees@outflux.net
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 framework that would allow the tests to build unmodified.
Kees Cook kees@outflux.net 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-devel/testing-windows don't have a method for doing the build with the free-of-charge windows CLI compiler (which the "STANDALONE" stuff works fine with).
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.
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. That should probably be noted somewhere in the FAQ. Also, perhaps the lz tests should be updated as well, since they are regularly mentioned as the basic example developers should work from.
-
Alexandre Julliard -
Dimitrie Paun -
Kees Cook