Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

MinGW, build GUI application with console

I'm using MinGW to build my application on Windows. When compiling and linking, the option "-mwindows" is put in command line to have Win32 API functions.

To be more specific: when calling GCC of MinGW without "-mwindows" like this:

c:\>g++ -c main.cpp 
c:\>g++ -o main.exe main.o

The 'main.exe' after the 2 command lines above will run with a console, and Win32 API functions won't be usable.

When calling GCC of MinGW with "-mwindows" like this:

c:\>g++ -c main.cpp
c:\>g++ -o main.exe main.o -mwindows

Now linking with '-mwindows', the 'main.exe' can use Win32 API, however, it doesn't start a console when the application runs.

This "-mwindows" option disables the console, which makes me not able to print out debugging info. Any way to keep both console and the option '-mwindows'?

like image 638
jondinham Avatar asked Oct 27 '12 13:10

jondinham


2 Answers

The -mconsole switch is used to specify that you want to target the console subsystem. You really do want to do that to ensure that your process connects to the existing console if started from a console app. For example, suppose you do go down your route of targeting the GUI subsystem, and then calling AllocConsole(), as per your own answer. Then you'll find your app shows a brand new console rather than using the existing one when started from another console app, e.g. cmd.exe.

If you need to use other libraries, then you are free to add them on command line using -l. There's nothing special about a console app that means that it cannot link to any Win32 API function. It's just that the default set of libraries associated with -mconsole is missing some of the libraries that you want.

On the other hand, you can use both -mconsole and -mwindows when you build your app. They are not mutually exclusive.

gcc -mconsole -mwindows main.c

This produces an application that targets the console subsystem. And you get the standard -mwindows set of Win32 libraries automatically linked. It's probably the simplest way to achieve your goal.

like image 67
David Heffernan Avatar answered Sep 19 '22 17:09

David Heffernan


I have no evidence for this answer, only a bit of experiments that were successful. If I have a hello app, like this:

#include <stdio.h>
#include <windows.h>

int main(void)
{
    puts("hi");
    MessageBox(NULL, "test", "test", NULL);
    GetStockObject(0);
    return 0;
}

I cannot compile it with -mconsole, because linker complains about GetStockObject. But when I add the necessary library with -lgdi32 switch on my command line, the app compiles and executes cleanly. Maybe this is the way to keep both console and gdi. This is the command line:

gcc -mconsole test_gdi.c -lgdi32
like image 35
Jarekczek Avatar answered Sep 19 '22 17:09

Jarekczek