Building winetest-latest.exe?

[Dan Kegel]

Hi folks,
how does one build the native version of winetest.exe?
I looked around a bit, and didn't see any obvious instructions.

http://www.winehq.org/pipermail/wine-devel/2011-July/091144.html
touches on it, but doesn't say much.

I ask because I'm interested in tracking down why testbot
doesn't think vcomp.dll is installed.
( cf. http://www.winehq.org/pipermail/wine-devel/2012-August/096642.html )
- Dan

[Vincent Povirk]

As I understand it, you need to set up a mingw build as in
http://wiki.winehq.org/CompilingDLLsUsingMingw

[Austin English]

On Sun, Sep 2, 2012 at 9:52 PM, Vincent Povirk  wrote:
> As I understand it, you need to set up a mingw build as in
> http://wiki.winehq.org/CompilingDLLsUsingMingw

Sort of. You don't need a separate build tree for building the tests.
Just have mingw32 installed, run ./configure, then 'make crosstest'.

[Dan Kegel]

On Mon, Sep 3, 2012 at 2:28 PM, Austin English  wrote:
> On Sun, Sep 2, 2012 at 9:52 PM, Vincent Povirk  wrote:
> > As I understand it, you need to set up a mingw build as in
> > http://wiki.winehq.org/CompilingDLLsUsingMingw
>
> Sort of. You don't need a separate build tree for building the tests.
> Just have mingw32 installed, run ./configure, then 'make crosstest'.

I've done 'make crosstest' many times, but building winetest.exe itself
does seem to require the two trees as described by that page.

(But as it turns out, the code I needed to fix was in buildbot,
not winetest.)
- Dan

[Francois Gouget]

On Mon, 3 Sep 2012, Dan Kegel wrote:
[...]
> > Sort of. You don't need a separate build tree for building the tests.
> > Just have mingw32 installed, run ./configure, then 'make crosstest'.
>
> I've done 'make crosstest' many times, but building winetest.exe itself
> does seem to require the two trees as described by that page.

For that one can also look at testbot/bin/buil/Reconfig.pl, 
specifically BuildNative() and BuildCross() (in the tools repository).
> (But as it turns out, the code I needed to fix was in buildbot,
> not winetest.)

Maybe the WineTestBot code needs a similar fix?
In testbot/src/TestLauncher/TestLauncher.c?

[Dan Kegel]

On Tue, Sep 4, 2012 at 3:18 PM, Francois Gouget  wrote:
> > (But as it turns out, the code I needed to fix was in buildbot,
> > not winetest.)
>
> Maybe the WineTestBot code needs a similar fix?
> In testbot/src/TestLauncher/TestLauncher.c?

Yeah, um, ^buildbot^testbot
I have a patch at
http://bugs.winehq.org/show_bug.cgi?id=31609
for your review.

[Francois Gouget]

On Tue, 4 Sep 2012, Dan Kegel wrote:
> On Tue, Sep 4, 2012 at 3:18 PM, Francois Gouget  wrote:
> > > (But as it turns out, the code I needed to fix was in buildbot,
> > > not winetest.)
> >
> > Maybe the WineTestBot code needs a similar fix?
> > In testbot/src/TestLauncher/TestLauncher.c?
>
> Yeah, um, ^buildbot^testbot
> I have a patch at
> http://bugs.winehq.org/show_bug.cgi?id=31609
> for your review.

Sorry about that. I forgot about you other email when replying to this 
one. From the bug report (so others may comment):

You're calling the functions directly instead of using the function 
pointers. Also it might be worth splitting the patch in two parts: one 
to introduce the 'goto done' which I feel is worth it on its own and the 
other for the activation context stuff. But then others might say this 
is overkill.

Otherwise I can't test the patch right now but it looks good.

[Francois Gouget]

On Sun, 2 Sep 2012, Vincent Povirk wrote:
> As I understand it, you need to set up a mingw build as in
> http://wiki.winehq.org/CompilingDLLsUsingMingw

The above page says to use mingw32 but this version of MinGW is pretty 
old (4.2) and, as far as I can tell, can only build 32bit Windows 
binaries. So I don't think that's what winetest / WineTestBot use.

I think nowadays the packages to use is gcc-mingw-w64 & co (currently 
4.6).

See also this discussion:
http://www.winehq.org/pipermail/wine-devel/2012-July/096183.html