On 05/02/2008, Jeremy White <[EMAIL PROTECTED]> wrote:
> > If some people went through the trouble of using buildid's and not the
> > precompiled winetest, along with documenting their hardware/OS on a
> > wiki page, for instance, then we could more information on where
> > specific failures are oc
Hi Jeremy,
Jeremy White wrote:
> Hi Paul,
>
>> Something we also have with the current tests is that the source files
>> actually
>> point to the correct version in CVS. I now see some strange links to refs on
>> http://test.winehq.org/data/20080205/.
>
> Well, I'm afraid I'd argue that the cur
> If some people went through the trouble of using buildid's and not the
> precompiled winetest, along with documenting their hardware/OS on a
> wiki page, for instance, then we could more information on where
> specific failures are occuring. For instance, I noticed Joapa was
> reporting some MSI
Jeremy White wrote:
> Hi Paul,
>
>> Something we also have with the current tests is that the source files
>> actually
>> point to the correct version in CVS. I now see some strange links to refs on
>> http://test.winehq.org/data/20080205/.
>
> Well, I'm afraid I'd argue that the current tests s
On Feb 5, 2008 10:30 AM, Paul Vriens <[EMAIL PROTECTED]> wrote:
> Hi,
>
> The good thing about having the winetest from one
> source(http://www.astro.gla.ac.uk/users/paulm/WRT/CrossBuilt/) is that all the
> output is actually from the same executable and it's easier to compare. If
> people are usin
Hi Paul,
> Something we also have with the current tests is that the source files
> actually
> point to the correct version in CVS. I now see some strange links to refs on
> http://test.winehq.org/data/20080205/.
Well, I'm afraid I'd argue that the current tests should be updated to point
to git
Jeremy White wrote:
> Okay, so I got winetest to do something rational, and now I'd like to see if
> it
> will work for someone else.
>
> It's easy!
>
> Just apply this patch to a current Wine tree:
> http://www.winehq.org/pipermail/wine-patches/2008-February/049675.html
>
> Then configure an
Okay, so I got winetest to do something rational, and now I'd like to see if it
will work for someone else.
It's easy!
Just apply this patch to a current Wine tree:
http://www.winehq.org/pipermail/wine-patches/2008-February/049675.html
Then configure and make Wine as you normally would. Then,
