Trying to fix a bug, stuck at cross-compiling

[Alexandru Băluț]

Hi,

I'm trying to fix bug 12804, and made some changes to winecfg, and I
need to test how it works on Windows. I followed the instructions from
http://wiki.winehq.org/CompilingDLLsUsingMingw - Cross Compiling the
Whole Tree, but I get an error:

$ ../wine-crossc/configure --host=i586-mingw32msvc
--with-wine-tools=../build-native --without-freetype --without-x
[...]
checking for the directory containing the Wine tools... configure:
error: could not find Wine tools in ../build-native

This seems to happen because the ../build-native/tools/winebuild
directory does not exist.

When I ran "make tools", in ../build-native, no error occurred. Any
idea why this happens?

Is there another way to build winecfg as an exe?

Thanks,
Alex

[Michael Stefaniuc]

Alexandru Băluț wrote:
> I'm trying to fix bug 12804, and made some changes to winecfg, and I
> need to test how it works on Windows. I followed the instructions from
> Just use the Wine Test Bot to test on Windows:
>   https://testbot.winehq.org/
> The corresponding wiki page is http://wiki.winehq.org/WineTestBot
> http://wiki.winehq.org/CompilingDLLsUsingMingw - Cross Compiling the
> Whole Tree, but I get an error:
>
> $ ../wine-crossc/configure --host=i586-mingw32msvc
> --with-wine-tools=../build-native --without-freetype --without-x
> [...]
> checking for the directory containing the Wine tools... configure:
> error: could not find Wine tools in ../build-native
>
> This seems to happen because the ../build-native/tools/winebuild
> directory does not exist.
>
> When I ran "make tools", in ../build-native, no error occurred. Any
> idea why this happens?
>
> Is there another way to build winecfg as an exe?
> Uhm, you want to test winecfg on Windows? That doesn't make much sense
> as winecfg is Wine specific.

bye	
	michael

[Alexandru Băluț]

Hi Michael,

The Wine Test Bot does not help. I need to test the interface of the
application.

Thanks,
Alex

On Mon, May 17, 2010 at 09:41, Michael Stefaniuc <mstefani(a)redhat.com> wrote:
> Alexandru Băluț wrote:
> > I'm trying to fix bug 12804, and made some changes to winecfg, and I
> > need to test how it works on Windows. I followed the instructions from
> > Just use the Wine Test Bot to test on Windows:
> >  https://testbot.winehq.org/
> > The corresponding wiki page is http://wiki.winehq.org/WineTestBot
> > http://wiki.winehq.org/CompilingDLLsUsingMingw - Cross Compiling the
> > Whole Tree, but I get an error:
> >
> > $ ../wine-crossc/configure --host=i586-mingw32msvc
> > --with-wine-tools=../build-native --without-freetype --without-x
> > [...]
> > checking for the directory containing the Wine tools... configure:
> > error: could not find Wine tools in ../build-native
> >
> > This seems to happen because the ../build-native/tools/winebuild
> > directory does not exist.
> >
> > When I ran "make tools", in ../build-native, no error occurred. Any
> > idea why this happens?
> >
> > Is there another way to build winecfg as an exe?
> > Uhm, you want to test winecfg on Windows? That doesn't make much sense
> > as winecfg is Wine specific.
>
> bye
>        michael

I'm also interested how to cross compile ;)

W.
> Hi Michael,
>
> The Wine Test Bot does not help. I need to test the
> interface of the
> application.
>
> Thanks,
> Alex

[André Hentschel]

Am 17.05.2010 14:04, schrieb Alexandru Băluț:
> Hi Michael,
>
> The Wine Test Bot does not help. I need to test the interface of the
> application.
>
> Thanks,
> Alex
>
> On Mon, May 17, 2010 at 09:41, Michael Stefaniuc <mstefani(a)redhat.com> wrote:
> > Alexandru Băluț wrote:
> > > I'm trying to fix bug 12804, and made some changes to winecfg, and I
> > > need to test how it works on Windows. I followed the instructions from
> > > Just use the Wine Test Bot to test on Windows:
> > >  https://testbot.winehq.org/
> > > The corresponding wiki page is http://wiki.winehq.org/WineTestBot
> > > http://wiki.winehq.org/CompilingDLLsUsingMingw - Cross Compiling the
> > > Whole Tree, but I get an error:
> > >
> > > $ ../wine-crossc/configure --host=i586-mingw32msvc
> > > --with-wine-tools=../build-native --without-freetype --without-x
> > > [...]
> > > checking for the directory containing the Wine tools... configure:
> > > error: could not find Wine tools in ../build-native
> > >
> > > This seems to happen because the ../build-native/tools/winebuild
> > > directory does not exist.
> > >
> > > When I ran "make tools", in ../build-native, no error occurred. Any
> > > idea why this happens?
> > >
> > > Is there another way to build winecfg as an exe?
> > > Uhm, you want to test winecfg on Windows? That doesn't make much sense
> > > as winecfg is Wine specific.
> >
> > bye
> >        michael

In my out of build tree i have a directory 00mingw. in there just type:
../configure --host=i586-mingw32msvc --with-wine-tools=../32/ --without-free
type host_alias=i586-mingw32msvc

(i have a directory "32" for wine32)
and the normal make stuff

winecfg has to much wine-specific stuff in it, so you have to cut that out.
i will send you a package of a cleaned winecfg, as i already did what you try.

-- 

Best Regards, André Hentschel

[Alexandru Băluț]

A workaround is to run "make" instead of "make tools" in build-native.

Alex

On Mon, May 17, 2010 at 03:36, Alexandru Băluț
<alexandru.balut(a)gmail.com> wrote:
> Hi,
>
> I'm trying to fix bug 12804, and made some changes to winecfg, and I
> need to test how it works on Windows. I followed the instructions from
> http://wiki.winehq.org/CompilingDLLsUsingMingw - Cross Compiling the
> Whole Tree, but I get an error:
>
> $ ../wine-crossc/configure --host=i586-mingw32msvc
> --with-wine-tools=../build-native --without-freetype --without-x
> [...]
> checking for the directory containing the Wine tools... configure:
> error: could not find Wine tools in ../build-native
>
> This seems to happen because the ../build-native/tools/winebuild
> directory does not exist.
>
> When I ran "make tools", in ../build-native, no error occurred. Any
> idea why this happens?
>
> Is there another way to build winecfg as an exe?
>
> Thanks,
> Alex