4

I've compiled a small app in Linux (Ubuntu 11.04) with Mingw32 and it runs ok in Wine, but does nothing on Wuindows (although it runs).

Configure:

./configure --host=i586-mingw32msvc --target=i586-mingw32msvc --build=i686-linux

(I've tried without --target and without --build with the same results.)

Compile:

i586-mingw32msvc-g++ -DHAVE_CONFIG_H -I. -I.. -DLOG_DOMAIN=\"tpv\" -I.. -DWINVER=0x0400 -D_WINDOWS_ -Wall -g -Wl,--subsystem,console -mconsole -mms-bitfields -g -O2 -MT tpv-excepciones.o -MD -MP -MF .deps/tpv-excepciones.Tpo -c -o tpv-excepciones.o

Link:

/bin/bash ../libtool --tag=CXX --mode=link i586-mingw32msvc-g++ -Wall -g -Wl,--subsystem,console -mconsole -mms-bitfields -g -O2 -lstdc++ -lgcc -lodbc32 -lwsock32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lctl3d32 -lodbc32 -ladvapi32 -lodbc32 -lwsock32 -lopengl32 -lglu32 -lole32 -loleaut32 -luuid -lmingw32 -Wl,-subsystem,console -o tpv.exe tpv-excepciones.o tpv-conf.o tpv-main.o

It generates an .exe file which is not a linux binary. It runs OK in wine, but does nothing in Windows XP.

Reading the web I've added some flags in configure time:

-Wl,--subsystem,console -mconsole -mms-bitfields

This is the program:

#include <windows.h>
#include "main.hh"


int main (int argc, char ** argv)
{
    MessageBox (0, "Joder!", "Ermmm...", MB_OK);

    //utils::conf c ("configuracion.3D");

    //std::cout << "Valor de 'no': '" << c["TEXTO_ERROR"] << "'" << std::endl;

    //std::cout << "..." << std::endl;

    return 0;
}

I've tried everything I've found on the web to no avail.

Am I missing something?

PeeHaa
  • 71,436
  • 58
  • 190
  • 262
Manuel
  • 2,526
  • 1
  • 13
  • 17
  • I've done cross compiling from my mac to windows, and I did not required any special flag. Try without anything, and with a simple example using directly mingw instead of configure and so on – Jaffa Oct 05 '11 at 10:25
  • 3
    my reputation here don't allow me a full response... so. The problem is **libtool**, the exe it creates in .libs dir works perfectly. – Manuel Oct 05 '11 at 14:49
  • Sounds like you are just not copying the MinGW32 CRT dlls across. – Steve-o Oct 05 '11 at 15:15
  • Have you tried using a debugger on windows with that cross-compiled binary? – Kos Jan 02 '12 at 15:04
  • Is it really supposed to be `main.hh` or `main.h` maybe? – Error withit Jan 02 '12 at 14:44

1 Answers1

1

Be sure to mark the application (in the PE32 executable header, I guess) as a "GUI" application, and not console. That is, use -mwindows with mingw (and not -mconsole). Your test source compiles fine (then it works) with this simple command (on Ubuntu 15.10 at least with deb package gcc-mingw-w64-i686 installed): i686-w64-mingw32-gcc -o test.exe test.c -mwindows.

I am far from being a Windows expert (not even a user too much ...), but as far as I know, Windows has a strict view that an application is console or GUI based, you can use the -mwindows switch to set this as "GUI application". I think, using a simple dialog box you've tried needs the application to be GUI based, and that could be the problem, that you haven't done that. A simple way to check your .exe:

lgb@antares:~$ file test.exe
test.exe: PE32 executable (GUI) Intel 80386, for MS Windows

Please note however, that a GUI application does not have console, so then you can't just printf() or other stdio functions to write to the console, because ... you haven't got a console :)

LGB Gábor Lénárt
  • 337
  • 2
  • 11