The example builds fine if I set the Subsystem setting to CONSOLE in linker settings. But I get command prompt blank window that way - I don't want that. Any idea as to how I can fix it now?
Thanks in advance, Asif On Fri, May 20, 2011 at 9:30 PM, asif saeed <[email protected]> wrote: > Hi Albrecht, > > I linking in fltkdlld.dll project in debug mode by *adding* that project in > the solution and adding its reference in the application that uses it. I > think it should not give me an error. Do you find anything wrong with that? > I have also specified the lib sub-directory of fltk in the Additional Linker > Directories setting. No success. > > Best regards, Asif > > > > On Fri, May 20, 2011 at 9:21 PM, asif saeed <[email protected]> wrote: > >> Hi again, >> >> I forgot to tell you that I trying to compile the example using Multi Byte >> Character Set setting (MBCS_) because I want to check compatibility with >> another library. After this code gets built ok, I'll write FLTK code to link >> my mani app with an existign lib which uses MBCS. May be this has to do with >> the linker error. >> >> Thanks, Asif >> >> >> >> On Fri, May 20, 2011 at 9:20 PM, asif saeed <[email protected]> wrote: >> >>> Hi again, >>> >>> I forgot to tell you that I am using Multi Byte Character Set setting >>> (MBCS_) >>> >>> >>> On Fri, May 20, 2011 at 9:18 PM, asif saeed <[email protected]> wrote: >>> >>>> I am trying to build the following example from this page >>>> http://www.fltk.org/doc-1.3/basics.html: >>>> >>>> #include <FL/Fl.H> >>>> #include <FL/Fl_Window.H> >>>> #include <FL/Fl_Box.H> >>>> >>>> int main(int argc, char **argv) { >>>> Fl_Window *window = new Fl_Window(340,180); >>>> Fl_Box *box = new Fl_Box(20,40,300,100,"Hello, World!"); >>>> box->box(FL_UP_BOX); >>>> box->labelfont(FL_BOLD+FL_ITALIC); >>>> box->labelsize(36); >>>> box->labeltype(FL_SHADOW_LABEL); >>>> window->end(); >>>> window->show(argc, argv); >>>> return Fl::run(); >>>> } >>>> >>>> I would thankful if you could help. >>>> >>>> Best regards, Asif >>>> >>>> >>>> On Fri, May 20, 2011 at 9:01 PM, asif saeed <[email protected]>wrote: >>>> >>>>> 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

