About building test suite for Windows

[Patrick Gauthier]

Hi,

As I was writing my task dialog test I ran into a few problems trying to
test on Windows...

First, I tried building it using make crosstest but I keep getting this:

$ gmake crosstest
crosstest is not supported (mingw not installed?)
gmake: *** [crosstest] Error 1

I am on FreeBSD 8.2-RELEASE (i386), I have the following mingw ports
installed (using pkg_add)

mingw32-bin-msvcrt-r3.18.a3.14
mingw32-binutils-2.21,1
mingw32-directx-20020518
mingw32-gcc-4.5.0_1,1
mingw32-pdcurses-3.4
mingw32-pthreads-2.8.0

I deleted config.status (there was no config.cache) and re-ran
./configure, it fails to detect mingw, so I gave up on that.

I then tried building them on Windows directly instead (using Visual
Studio 2008 with Windows SDK v7.0) as describred there:
http://www.winehq.org/docs/winedev-guide/testing-windows

However, trying to compile comctl32_tests using the WINE headers would
complain about EXCEPTION_EXECUTE_HANDLER being undefined. On the other
hand, compiling with the MSVC headers would complain about TVIS_FOCUSED
not being present. According to this:
http://support.microsoft.com/kb/166471 it has been deprecated and
removed from MS headers a long time ago.

Eventually I would like to just be able to make crosstest so that I can
stay in one dev environments and not two, so if anybody could help me
about why isn't mingw32 detected, I would like it.

Thanks.
- Patrick

[Maarten Lankhorst]

Op 12-06-11 07:54, Patrick Gauthier schreef:
> Hi,
>
> As I was writing my task dialog test I ran into a few problems trying to
> test on Windows...
>
> First, I tried building it using make crosstest but I keep getting this:
>
> $ gmake crosstest
> crosstest is not supported (mingw not installed?)
> gmake: *** [crosstest] Error 1
>
> I am on FreeBSD 8.2-RELEASE (i386), I have the following mingw ports
> installed (using pkg_add)
>
> mingw32-bin-msvcrt-r3.18.a3.14
> mingw32-binutils-2.21,1
> mingw32-directx-20020518
> mingw32-gcc-4.5.0_1,1
> mingw32-pdcurses-3.4
> mingw32-pthreads-2.8.0
> What is your mingw prefix?

~Maarten

[André Hentschel]

Am 12.06.2011 07:54, schrieb Patrick Gauthier:
> Hi,
>
> As I was writing my task dialog test I ran into a few problems trying to
> test on Windows...
>
> First, I tried building it using make crosstest but I keep getting this:
>
> $ gmake crosstest
> crosstest is not supported (mingw not installed?)
> gmake: *** [crosstest] Error 1
>
> I am on FreeBSD 8.2-RELEASE (i386), I have the following mingw ports
> installed (using pkg_add)
>
> mingw32-bin-msvcrt-r3.18.a3.14
> mingw32-binutils-2.21,1
> mingw32-directx-20020518
> mingw32-gcc-4.5.0_1,1
> mingw32-pdcurses-3.4
> mingw32-pthreads-2.8.0
>
> Eventually I would like to just be able to make crosstest so that I can
> stay in one dev environments and not two, so if anybody could help me
> about why isn't mingw32 detected, I would like it.

Hi,
i had a look in my config.log and found in my 32-bit tree:
...
configure:7022: checking for i686-mingw32msvc-gcc
configure:7052: result: no
configure:7022: checking for i586-mingw32msvc-gcc
configure:7038: found /usr/bin/i586-mingw32msvc-gcc
configure:7049: result: i586-mingw32msvc-gcc
configure:7065: checking whether i586-mingw32msvc-gcc works
configure:7078: i586-mingw32msvc-gcc -c -g -O2  conftest.c >&5
configure:7078: $? = 0
configure:7079: result: yes
...

so i had a look at configure and if i understand it correct it simply searches for one of these in your $PATH:
i686-w64-mingw32-gcc i586-w64-mingw32-gcc i486-w64-mingw32-gcc i386-w64-mingw32-gcc
i686-pc-mingw32-gcc i586-pc-mingw32-gcc i486-pc-mingw32-gcc i386-pc-mingw32-gcc
i686-mingw32msvc-gcc i586-mingw32msvc-gcc i486-mingw32msvc-gcc i386-mingw32msvc-gcc
i686-mingw32-gcc i586-mingw32-gcc i486-mingw32-gcc i386-mingw32-gcc

so to state Maartens question more precisely: where is your mingw32-gcc binary, what's its name and is its path in your $PATH?

-- 

Best Regards, André Hentschel

[Patrick Gauthier]

On 06/12/11 07:03, André Hentschel wrote:
> Hi,
> i had a look in my config.log and found in my 32-bit tree:
> ...
> configure:7022: checking for i686-mingw32msvc-gcc
> configure:7052: result: no
> configure:7022: checking for i586-mingw32msvc-gcc
> configure:7038: found /usr/bin/i586-mingw32msvc-gcc
> configure:7049: result: i586-mingw32msvc-gcc
> configure:7065: checking whether i586-mingw32msvc-gcc works
> configure:7078: i586-mingw32msvc-gcc -c -g -O2  conftest.c >&5
> configure:7078: $? = 0
> configure:7079: result: yes
> ...
>
> so i had a look at configure and if i understand it correct it simply searches for one of these in your $PATH:
> i686-w64-mingw32-gcc i586-w64-mingw32-gcc i486-w64-mingw32-gcc i386-w64-mingw32-gcc
> i686-pc-mingw32-gcc i586-pc-mingw32-gcc i486-pc-mingw32-gcc i386-pc-mingw32-gcc
> i686-mingw32msvc-gcc i586-mingw32msvc-gcc i486-mingw32msvc-gcc i386-mingw32msvc-gcc
> i686-mingw32-gcc i586-mingw32-gcc i486-mingw32-gcc i386-mingw32-gcc
>
> so to state Maartens question more precisely: where is your mingw32-gcc binary, what's its name and is its path in your $PATH?

My mingw32-gcc is in /usr/local/bin, its name is simply "mingw32-gcc"
(no CPU name in there) and yes it's in $PATH.

On 06/12/11 07:10, Nicolas Le Cam wrote:
> If I read the port's makefile right, using ./configure
> CROSSCC="mingw32-gcc" should help.

I tried this actually, and indeed the makefile stopped complaining, then
winebuild started doing this instead:

winebuild: Invalid target specification 'mingw32'

A quick look in tools/winebuild/main.c (function set_target, line 194)
shows that it chokes if the target specification does not contain at
least one dash.

Now I am wondering if it's my system which is at fault for being badly
configured or if I should just modify winebuild so that it is more
lenient in its parsing of the target?

Thanks,
- Patrick

[Alexandre Julliard]

Patrick Gauthier <webmaster(a)korosoft.net> writes:
> Now I am wondering if it's my system which is at fault for being badly
> configured or if I should just modify winebuild so that it is more
> lenient in its parsing of the target?

You should fix your mingw package. We need a cpu name to know which
architecture is supported, since there's a 64-bit mingw too.

-- 
Alexandre Julliard
julliard(a)winehq.org

[Nicolas Le Cam]

2011/6/12 Patrick Gauthier <webmaster(a)korosoft.net>:
> Hi,
>
> As I was writing my task dialog test I ran into a few problems trying to
> test on Windows...
>
> First, I tried building it using make crosstest but I keep getting this:
>
> $ gmake crosstest
> crosstest is not supported (mingw not installed?)
> gmake: *** [crosstest] Error 1
>
> I am on FreeBSD 8.2-RELEASE (i386), I have the following mingw ports
> installed (using pkg_add)
>
> mingw32-bin-msvcrt-r3.18.a3.14
> mingw32-binutils-2.21,1
> mingw32-directx-20020518
> mingw32-gcc-4.5.0_1,1
> mingw32-pdcurses-3.4
> mingw32-pthreads-2.8.0
>
> I deleted config.status (there was no config.cache) and re-ran
> ./configure, it fails to detect mingw, so I gave up on that.
>
> I then tried building them on Windows directly instead (using Visual
> Studio 2008 with Windows SDK v7.0) as describred there:
> http://www.winehq.org/docs/winedev-guide/testing-windows
>
> However, trying to compile comctl32_tests using the WINE headers would
> complain about EXCEPTION_EXECUTE_HANDLER being undefined. On the other
> hand, compiling with the MSVC headers would complain about TVIS_FOCUSED
> not being present. According to this:
> http://support.microsoft.com/kb/166471 it has been deprecated and
> removed from MS headers a long time ago.
>
> Eventually I would like to just be able to make crosstest so that I can
> stay in one dev environments and not two, so if anybody could help me
> about why isn't mingw32 detected, I would like it.
>
> Thanks.
> - Patrick

If I read the port's makefile right, using ./configure
CROSSCC="mingw32-gcc" should help.

-- 
Nicolas Le Cam