Why can't anybody understand that GCC outputs the same exact machine code language that an assembler outputs? Anything *any* compiler in the world outputs, an assembly language can output, but not vice versa. The only prerequisite required is that you must understand how the compiler and the target OS works at the assembly level.
I am an assembly language programmer so I don't need any assembly language GTK+ examples. Like I said, I have an assembly language program for the Win32 GTK+ v3.18 package that has buttons and file choosers and dialogs ... all working as expected. I only have a problem with the command line arguments not being passed to my program. On 4/16/2016 at 3:44 AM, Florian Pelz <pelzflor...@pelzflorian.de> wrote: >On 04/16/2016 10:53 AM, Lucas Levrel wrote: >> Gtk2 came with "gtk-demo". Doesn't Gtk3 have a similar app? However, I >> don't know if it parses command-line args, if that's what you're looking >> for. > >It is called gtk3-demo and it doesn't parse command-line args because >its examples are not run from the command-line. AFAIK gtk_init will >probably lose it's command-line parsing ability anyway and use only >environment variables instead. I'm not sure though. Of course >command-line parsing can still be useful for the application itself. > >Probably it wouldn't help Andrew anyway because gtk3-demo is written in >C and the GoDev tools don't include a C compiler. What Andrew is asking >for is a GoAsm assembly language GTK+ example program if I'm not mistaken. > >_______________________________________________ >gtk-app-devel-list mailing list >gtk-app-devel-list@gnome.org >https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
