Re[2]: argv

["Andrew Robinson" <arobinson18 cox net>]

Just so there is no misunderstandings here, I want everyone to realize that
when a typical GTK+ program is selected from Windows Explorer:

1) A DOS CLI window appears
2) After a short delay, the GTK+ program appears

If you leave off the "/console" option on compilation, the DOS CLI does not
appear, but when you exit your GTK+ program, it will still be running in the
background. The only way to close it then, is to open Windows Task Manager and
kill the thread for your GTK+ application. With the "/console" option, closing
the GTK+ program still leaves the DOS CLI open and the Task Manager still
shows your program running, but when you close the DOS CLI, the program
completely exits.

This sequence of operations is why I believe Windows is "stealing" my command
line args and passing on something else that is nonsense, or that the only
real way to get the command line args with Win32 GTK+ programs is to not use
the args, but to use g_application_new(G_APPLICATION_HANDLES_COMMAND_LINE).

Thanks,

Andrew 

On 4/15/2016 at 11:35 AM, Florian Pelz <pelzflorian pelzflorian de> wrote:
> On 04/12/2016 01:58 PM, David Marceau wrote:
> > If you really need to resort to assembler, just run the gcc/g++ compiler
> > with the "-c -S" to generate the assembler to see how they gcc compiler
> > does it with the above gtkhello.c
>
> This here really is good advice. If you don't want to read GNU assembler
> language, then make gcc output Intel assembler syntax (see [1]).
>
> That said, you are asking for advice on a GTK+ list when your problems
> apparently have nothing to do with GTK+.
>
> [1]
> https://stackoverflow.com/questions/199966/how-do-you-use-gcc-to-generate-assembly-code-in-intel-syntax