Don't compile winetest as part of the main build

Saulius Krasuckas saulius2 at
Thu Aug 26 04:27:15 CDT 2004

On Thu, 26 Aug 2004, Rein Klazes wrote:
> On Wed, 25 Aug 2004 16:04:52 +0100, you wrote:
> > Was this dropped? On my laptop (a 600mhz Pentium with 128mb of ram, so 
> > not too pokey) attempting to build the winetest binary actually kills 
> > the build dead. It ends up attempting to feed ~20mb of data to gas which 
> > doesn't make it very happy. I guess I misphrased it - it's not for 
> > slower machines, it's for machines with less memory.
> I have recently built wine on a P1-133 with 64MB of memory (with
> success). 
> You should never be out of memory with enough swap.

In my case it is a free space on the "/" filesystem which I get running
out of.  Knowing the fact I like to live with a very small amount of a
free space on the "/" I should complain only to myself.

On Wed, 25 Aug 2004, Alexandre Julliard wrote:
> Mike Hearn <m.hearn at> writes:
> > There's not much reason to run the entire winetest binary on Wine
> > itself, so why do we always build it ?
> Because code that doesn't get built rots very quickly. You can disable
> it in your tree, but the default should be to build it.

And how exactly can I disable it?  By editing wineinstall script?

More information about the wine-devel mailing list