From: tomdean <to...@sp...> - 2012-05-11 00:38:43
|
I forget the reason.... When I double click on a .exe, I get a command window plus whatever application window I created. Why? Tom Dean |
From: tomdean <to...@sp...> - 2012-05-11 00:52:45
|
Memory came back One app did not ShowWindow(...) or UpdateWindow(...) Tom Dean |
From: tomdean <to...@sp...> - 2012-05-11 00:55:59
|
On 5/10/2012 5:52 PM, tomdean wrote: > Memory came back > > One app did not ShowWindow(...) or UpdateWindow(...) > Or, maybe the memory left again. That was not it. Tom Dean |
From: Luis L. <lui...@gm...> - 2012-05-11 01:00:45
|
On Thu, May 10, 2012 at 9:55 PM, tomdean <to...@sp...> wrote: > On 5/10/2012 5:52 PM, tomdean wrote: >> Memory came back >> >> One app did not ShowWindow(...) or UpdateWindow(...) >> > Or, maybe the memory left again. That was not it. > Use gcc -mwindows, by default it will create a console application. See gcc --target-help -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exupéry |
From: tomdean <to...@sp...> - 2012-05-11 01:50:08
|
On 5/10/2012 6:00 PM, Luis Lavena wrote: > Use gcc -mwindows, by default it will create a console application. > See gcc --target-help I am using 'g++ -I. -lgdi32 -lcomctl32 -lcomdlg32 <filename>.cpp -o <filename>' When I double click on <filename>.exe, a command window opens then whatever window I create opens. Tom Dean |
From: Ruben V. B. <van...@gm...> - 2012-05-11 06:20:34
|
Op 11 mei 2012 03:50 schreef "tomdean" <to...@sp...> het volgende: > > On 5/10/2012 6:00 PM, Luis Lavena wrote: > > Use gcc -mwindows, by default it will create a console application. > > See gcc --target-help > I am using 'g++ -I. -lgdi32 -lcomctl32 -lcomdlg32 <filename>.cpp -o > <filename>' > > When I double click on <filename>.exe, a command window opens then > whatever window I create opens. > Use 'g++ -mwindows -lgdi32 -lcomctl32 -lcomdlg32 <filename>.cpp -o <filename>' instead. If you leave out -mwindows, GCC defaults to -mconsole and you get a console window. The same applies to msvc with the /subsystem commandline option. Ruben > Tom Dean > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Mingw-w64-public mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public |
From: Earnie B. <ea...@us...> - 2012-05-11 12:57:21
|
On Fri, May 11, 2012 at 2:20 AM, Ruben Van Boxem <van...@gm...> wrote: > Op 11 mei 2012 03:50 schreef "tomdean" <to...@sp...> het volgende: > > >> >> On 5/10/2012 6:00 PM, Luis Lavena wrote: >> > Use gcc -mwindows, by default it will create a console application. >> > See gcc --target-help >> I am using 'g++ -I. -lgdi32 -lcomctl32 -lcomdlg32 <filename>.cpp -o >> <filename>' >> >> When I double click on <filename>.exe, a command window opens then >> whatever window I create opens. >> > > Use 'g++ -mwindows -lgdi32 -lcomctl32 -lcomdlg32 <filename>.cpp -o > <filename>' instead. If you leave out -mwindows, GCC defaults to -mconsole > and you get a console window. The same applies to msvc with the /subsystem > commandline option. Isn't the library specification order incorrect and perhaps not needed? -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Kai T. <kti...@go...> - 2012-05-11 13:32:46
|
2012/5/11 Earnie Boyd <ea...@us...>: > On Fri, May 11, 2012 at 2:20 AM, Ruben Van Boxem > <van...@gm...> wrote: >> Op 11 mei 2012 03:50 schreef "tomdean" <to...@sp...> het volgende: >> >> >>> >>> On 5/10/2012 6:00 PM, Luis Lavena wrote: >>> > Use gcc -mwindows, by default it will create a console application. >>> > See gcc --target-help >>> I am using 'g++ -I. -lgdi32 -lcomctl32 -lcomdlg32 <filename>.cpp -o >>> <filename>' >>> >>> When I double click on <filename>.exe, a command window opens then >>> whatever window I create opens. >>> >> >> Use 'g++ -mwindows -lgdi32 -lcomctl32 -lcomdlg32 <filename>.cpp -o >> <filename>' instead. If you leave out -mwindows, GCC defaults to -mconsole >> and you get a console window. The same applies to msvc with the /subsystem >> commandline option. > > Isn't the library specification order incorrect and perhaps not needed? > > -- > Earnie Well, the order of the libraries is incorrect, but also bogus. Therefore no harm is caused by this. The gcc frontend adds auto-magically the libraries in proper order - see output of frontend with -v option. If you don't want console then build GUI mode, means use the -mwindows option. Kai |