Err... putting main as the entry point is not good as that does not end my application when I close the example app. I await your help.
-Asif On Fri, May 20, 2011 at 8:56 PM, asif saeed <[email protected]> wrote: > Hi again, > > I solved this by going to Project Properties -> Configuration Properties -> > Linker -> Advanced and putting "main" as the value for the "Entry Point" > field. > > Is there any simpler alternative that you would like to suggest. I got the > above help from an internet forum but may be this is not right and may be > there is a better option. Any help? > > Best, asif > > > > > > > On Fri, May 20, 2011 at 8:50 PM, asif saeed <[email protected]> wrote: > >> Hi Albrecht, >> >> Now I am getting this error: >> >> 2>MSVCRTD.lib(crtexew.obj) : error LNK2019: unresolved external symbol >> _WinMain@16 referenced in function ___tmainCRTStartup >> 2>E:\scratch\ttt\Debug\ttt.exe : fatal error LNK1120: 1 unresolved >> externals >> >> I am using fltk-1.3.x-r8514 with Visual C++ 2010 Express. The fltddlld.dll >> gets built ok. I get this linker error only at the very end. >> >> Thanks in advance for the help. >> >> Asif >> >> >> On Fri, May 20, 2011 at 8:34 PM, Albrecht Schlosser < >> [email protected]> wrote: >> >>> On 20.05.2011 16:58, asif saeed wrote: >>> >>> > I am trying to use E:\libs\fltk-1.3.x-r8514\test\fltkdlld.dll (that I >>> built >>> > using the debug config) with my own application that I initially >>> created as >>> > an empty Win32 project. The application gives me the following error: >>> > >>> > Unhandled exception at 0x5f43351b (MFC42D.DLL) in nctrf5.exe: >>> 0xC0000005: >>> > Access violation reading location 0x00000000. >>> >>> Sorry, I probably can't help with this, but maybe this advice can help: >>> Be consistent with your linker options (/MD and /MT come to mind), and >>> use the correct .lib and .dll files that belong together and have been >>> built with the same options as your .exe. In case of doubt, clean the >>> whole project and build it again... >>> >>> > My library is also using MFC - which I have isolated successfully. I >>> need to >>> > make it a Win32 application and NOT a console application - basically, >>> do >>> > not want to get blank (and black) command-prompt windows along with my >>> GUI >>> > application. Any help? >>> >>> There's a linker option somewhere to make your exe either a console or a >>> windows application, something like /subsystem:console vs. >>> /subsystem:windows. >>> The latter is what you want. >>> >>> WRT to using MFC together with FLTK I don't know if this would work, and >>> maybe nobody else here will know. You're probably on your own with this. >>> >>> Albrecht >>> _______________________________________________ >>> fltk mailing list >>> [email protected] >>> http://lists.easysw.com/mailman/listinfo/fltk >>> >> >> > _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
