[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
libmwin
From: Kees Schoenmakers ####@####.#### Date: 24 Oct 2011 15:19:07 -0000 Message-Id: <201110241718.47908.k.schoenmakers@sigmae.nl> Hi Greg, If I (cross)build microwindows (full snapshot) for ARM and I try to use the libraries for an application It get an unresolved error. Looking at lib/libmwin.so with nm gives: 0004e280 T ValidateRect 0004e374 T ValidateRgn U WinMain <<-------------- 0004f664 T WindowFromPoint 0008cbb0 b ZeroDataBlock If I comment out the line in mwin/winmain.c where the call to WinMain is made everything appears fine. (about line 115) Do I miss something here? best regards, Kees | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] libmwin
From: "Greg Haerr" ####@####.#### Date: 31 Oct 2011 22:46:59 -0000 Message-Id: <054b01cc981e$cdbe66b0$0300a8c0@RDP> : If I (cross)build microwindows (full snapshot) for ARM and I try to use the : libraries for an application It get an unresolved error. Looking at : lib/libmwin.so with nm gives: : : If I comment out the line in mwin/winmain.c where the call to WinMain is : made everything appears fine. (about line 115) Kees - Yes, the call to WinMain is the call to YOUR application. The entry point for win32 applications is WinMain, not main. Microwindows uses the same approach. The win32 "applications" actually contain all the windowing code and draw directly to the framebuffer. The main() entry point is called in mwin/winmain.c, and that code then calls WinMain, an external, to start running your code. Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] libmwin
From: Kees Schoenmakers ####@####.#### Date: 7 Nov 2011 07:47:26 -0000 Message-Id: <201111070847.10292.k.schoenmakers@sigmae.nl> > > Yes, the call to WinMain is the call to YOUR application. The > entry point for win32 applications is WinMain, not main. Microwindows > uses the same approach. The win32 "applications" actually contain > all the windowing code and draw directly to the framebuffer. The > main() entry point is called in mwin/winmain.c, and that code then > calls WinMain, an external, to start running your code. > > Regards, > > Greg Greg, Would 'ApplicationMain' in the place of 'WinMain' not be more clear, as 'Win' is a little ambigious name in my view. best regards Kees | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] libmwin
From: "Greg Haerr" ####@####.#### Date: 9 Nov 2011 18:23:19 -0000 Message-Id: <C203C5A6D02E468593134F4A2C3517E8@winXP> : Would 'ApplicationMain' in the place of 'WinMain' not be more clear, : as 'Win' is a little ambigious name in my view. I didn't invent the names - they are exactly compatible with Microsoft Win32 application programming interface. If you change the names, then programs won't compile unchanged. Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |