Re: How can I loose the cmd window from my GtkAda app?

[Jack Mitchell <jack@plus.com>]

As something of a newby, I added the -nwindows option only on the 
production builds (I have a debug package which writes to file and to 
the console if stdout is open)

E.G.

    package Linker is
       ...........
       case Mode is
          when "Debug" =>

          when "Production" =>
             for Default_Switches ("ada") use Linker'Default_Switches 
("-mwindows");
       end case;
    end Linker;





In message <w9hl8hae9g57$.ry62m3ommmaw.dlg@40tude.net>, Dmitry A. 
Kazakov <mailbox@dmitry-kazakov.de> writes
>On Tue, 12 May 2009 10:13:04 +0200, Jean-Pierre Rosen wrote:
>
>> Dmitry A. Kazakov a �crit :
>>> Yes, however I would prefer to have it enforced by gtkada.gpr, rather than
>>> contaminating the application's gpr which with-es gtkada.gpr. Unfortunately
>>> I know no way to do this in a library project.
>>>
>> I don't think it would be a good idea, because sometimes you do want
>> that window (to get simple traces with Text_IO for example). And (AFAIK)
>> there is no option to cancel a -mwindows option.
>
>Using standard output is kind of "erroneous" in gtkada applications. Under
>Windows it will most likely crash the application (due to Use_Error, I
>guess).
>
>For tracing I am using a GTK window, which is much simpler than text
>tracing. It also allows to stop the application at the tracing point, catch
>GTK/Glib errors with stack backtracing etc.
>
>BTW, when running under GPS, output to the standard output works even with
>-mwindows.
>
>But the point was that -mwindows is just one example of what a library
>project could like to pass to the clients.
>

-- 
Jack Mitchell