Re: argv revisited

Il Mon, 9 May 2016 09:35:06 -0500 Edscott Wilson scrisse: > ... > Many thanks to all those who have responded. With all the advice I'm now > going to try cross compiling 64 bit GTK application for windows using all > the tools available in ArchLinux and the AUR

Re: argv revisited

2016-05-08 13:41 GMT-05:00 tito-wolit : > If you don't like the advice being given by the experts on this list > why you are still hanging around here? > > Because he's a troll who gets a dopamine hit when someone answers. But I must admit that he is polite and

Re: argv revisited

On 05/08/2016 05:45 PM, Andrew Robinson wrote: Like most people in this forum, you don't listen: My issue isn't with GTK2, it is with GTK3. I know Fedora has precompiled GTK2 binaries but doesn't help me with GTK3. My original issue is clearly stated as using the following

Re: argv revisited

Welcome to my Trash folder; you'll be directed there by the filter I just put in place. Watch out for the falling banana peels. On 05/08/16 12:24, Andrew Robinson wrote: Because you are entertaining. On 5/8/2016 at 9:09 AM, Chris Moller wrote: If you don't like the

Re: argv revisited

If you don't like the people on this forum, and you don't like the answers you've gotten, why are you still here? On 05/08/16 11:45, Andrew Robinson wrote: Like most people in this forum, you don't listen: My issue isn't with GTK2, it is with GTK3. I know Fedora has precompiled

Re: argv revisited

On 04/30/2016 11:25 PM, Andrew Robinson wrote: > My initial request for help in this forum was that main(argc,argv) only > returned garbage instead of the command line when using the 32-bit version of > GTK+ v3.18 on a 64-bit Windows7 OS. This forum was unable to offer any expert > help or advice

Re: argv

Andrew, On 4/16/2016 at 1:47 PM, Enno Borgsteede wrote: 1) Argc and argv are initially processed only by the OS, and never by the linker or GTK or any compiler until after main() is called. Nothing you can do with the linker, GTK, or the compiler can change that fact.

Re: argv

Andrew Robinson wrote: > > The AddressOfEntryPoint is 0088 and is determined by me. The entry point > is therefore always the same. I may be misunderstanding the problem; but if you're implementing the startup code yourself, don't you need to call GetCommandLine() in

Re: argv

Howdy, Andrew Robinson wrote: > This should be easy, but it is not. I am writing an assembly language program > involving GTK+. I want to parse the command line for options but am unable to > do so. The code to find argv and argc is simple: > > main: >push ebp >mov ebp, esp >lea eax,

Re: argv

Andrew, In reality, this is what it actually is: 1) Argc and argv are initially processed only by the OS, and never by the linker or GTK or any compiler until after main() is called. Nothing you can do with the linker, GTK, or the compiler can change that fact. Not true. The program arguments

Re: argv

YES there are two different calling conventions used in older win32 applications they push/pop the args in different orders in the assembler part essentially. http://unixwiz.net/techtips/win32-callconv.html 1)PASCAL calling convention(preferred legacy WINAPI calling convention) "The other most

Re: argv

On 04/16/2016 07:59 PM, Andrew Robinson wrote: > Don't forget that GTK is already running on top of the Windows command line > and therefore I have no direct access to it. Everything is processed by GTK > before I can ever get to it for myself. > > I do suspect that Windows may be the cause of

Re: argv

On 04/16/2016 06:50 PM, Andrew Robinson wrote: > Assembly language has no calling convention whatsoever until you hand code it > to have whatever calling convention you want it to have, preferably matching > the calling convention of whatever you are interfacing to. > This is not a matter of

Re: argv

On 04/16/2016 06:23 PM, Andrew Robinson wrote: > That is completely incorrect. By definition, main(argc,argv) means that before > you add even one line of code, argc and argv are on the stack, ready to be > used. That's how it should be in C, but not necessarily in assemblers. Since you seem to

Re: argv

Mr. Robinson, My original email was verbose so it never made it to the mailing list so I decided to send it directly to you. I didn't realize you're were going to be upset with the entire community because of my answer. There was no condescending or tone of superiority ever conveyed in that

Re: argv

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

Re: argv

GTK+ has no influence on the command line until you call gtk_init on it, after which a valid command line remains a valid command line. Your problem is not related to GTK+. What influences the command line is the way GoLink calls main, so you should be asking your question on the GoDev forum.

Re: argv

On 04/15/2016 09:59 PM, Andrew Robinson wrote: > I may be the only person writing a > program in GoAsm for for GTK+3 and cross-OS, but that has nothing to do with > my problem. That you use GoAsm and GoLink instead of GCC can make a difference. Different build toolchains may not be compatible.

Re: argv

On 04/15/2016 09:30 PM, Mark Cianfaglione wrote: > […] > To the community's defense I have to say that I've never seen anyone use > ANY Gtk from assembler in the 7+ years that I've been using it. (Other > than what is compiled from GCC.) > > Sounds like you are breaking new ground. Do keep the

Re: argv

On 15/04/16 03:17 PM, Andrew Robinson wrote: It is good advice but do you have a *working* or *tested* example that I can do this with using the GTK+ Win32 libraries? I don't and that is my problem and it is one hundred percent a GTK+ problem because I am only using GTK+ for my program. To the

Re: argv

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

Re: argv

On Sat, 9 Apr 2016 18:39:49 -0700 "Andrew Robinson" wrote: > The problem is that [ebp + 12] and [ebp + 8] point to nonsense. I ran a > debugger and looked at the stack, and there is nothing else on the stack > except for ebp, rtn addr, and these two parameters. I even tried

Re: argv

Taken from an older gtk tutorial, but nevertheless should apply to your situation: http://www.gtk.org/tutorial1.2/gtk_tut-2.html #include int main( int argc, char *argv[] ) { GtkWidget *window; //<<< //DID YOU INTRODUCE THIS LINE IN YOUR CODE?