On Tue, 2006-10-03 at 20:58 -0400, Allin Cottrell wrote:
> Use Mingw gcc with the -mwindows flag.
Yes mingw gcc on windows will create a non-console application with only
a main() just fine. No WinMain required.
>
> Allin Cottrell
> ___
> gtk-app-deve
On Tue, 2006-10-03 at 16:19, Christopher Backhouse wrote:
> Lots of my code has this at the top of it
>
> #pragma comment(linker, "/subsystem:\"windows\"
> /entry:\"mainCRTStartup\"") //Kill console window
>
> I got it off the internet somewhere.
> I assume the unrecognised pragma will be ignor
On Tue, 3 Oct 2006, Alan M. Evans wrote:
> On Tue, 2006-10-03 at 11:06, Tor Lillqvist wrote:
>> If the linker insists on it, add a WinMain() then?
>
> Of course. But I resist this for aesthetic reasons. Thanks largely to
> the cross-platform nature of GLib and GTK+, my application currently has
>
Lots of my code has this at the top of it
#pragma comment(linker, "/subsystem:\"windows\"
/entry:\"mainCRTStartup\"") //Kill console window
I got it off the internet somewhere.
I assume the unrecognised pragma will be ignored by every other compiler
out there so it should be "portable" (if a l
On Tue, 2006-10-03 at 14:52, Reed Hedges wrote:
> Are you using cygwin or mingw?
Nope. Just took my prog developed on my Linux workstation and created a
VC++ project by adding the source files and specifying the Win32
glib/gtk+ libs and DLLs.
___
gtk-a
Are you using cygwin or mingw?
Alan M. Evans wrote:
> On Tue, 2006-10-03 at 11:06, Tor Lillqvist wrote:
>> If the linker insists on it, add a WinMain() then?
>
> Of course. But I resist this for aesthetic reasons. Thanks largely to
> the cross-platform nature of GLib and GTK+, my application c
On Tue, 2006-10-03 at 11:06, Tor Lillqvist wrote:
> If the linker insists on it, add a WinMain() then?
Of course. But I resist this for aesthetic reasons. Thanks largely to
the cross-platform nature of GLib and GTK+, my application currently has
no #ifdef for platform-specific code.
The thing is,
Alan M. Evans writes:
> In that case it fails to link with WinMain, which of course doesn't exist.
If the linker insists on it, add a WinMain() then? It can be as simple
as:
#include
#include
int _stdcall
WinMain (struct HINSTANCE__ *hInstance,
struct HINSTANCE__ *hPrevInstance,
On Tue, 2006-10-03 at 09:12, Tor Lillqvist wrote:
> add "/subsystem:windows" to the linking options. (If using gcc, it
> would be "-mwindows".) Or run "editbin /subsystem:windows" on the .exe
> file any time after linking.
I find that doing the former doesn't actually work. In that case it
fails t
Matthew Yaconis writes:
> I have a natively linux GTK+ application that I've ported to Win32 using
> MSVC++. The way I originally ported it causes the cmd window (that catches
> all the printf type statements) to appear whenever running the application.
> I thought there was some way to disabl
I have a natively linux GTK+ application that I've ported to Win32 using
MSVC++. The way I originally ported it causes the cmd window (that catches
all the printf type statements) to appear whenever running the application.
I thought there was some way to disable this but haven't been able to find
11 matches
Mail list logo
