Page 2 of 2
Posted: Sun Nov 13, 2005 3:38 am
by afecelis
right where your executable is. Or if you want to be able to run Irrlicht exes from anywhere in your system place it in C:\windows\system32, just remember to replace it with any newer versions you develop.
Posted: Sat Jan 28, 2006 3:02 pm
by Guest
HEY IT´S ME THE DOGPOUND I GOT A PROBLEM WITH THE USER INTEFACE
WHEN I FINISHED CORRECTING ALL THE MISTAKES THAT I HAD I GENERATED THE CODE EVERYTHING WENT FINE TILL I STARTED IT AND THE ERROR MESSAGE CANNOT FIND PROCEIDURE ENTRY POINT:?createDevice@irr@@YAPAVirrlichtDevice@14WE_DRIVER_TYPE@video@1@ABV?$dimiension2d@H@core@1@I-N22PAVIEventReceiver@1@PBG@Z in the irrlicht.dll dinamic library
Posted: Sun Jan 29, 2006 11:27 am
by Nick_Japan
I think that's usually when one of the header (ie Irrlicht.h), the library file or the dll you are using are different versions - make sure that all the library / include directories point to the same version of Irrlicht and make sure that same version of Irrlicht's dll is in your project's directory.
Posted: Fri Feb 10, 2006 3:05 am
by Guest
error LNK2019: External symbol_main without being solved to wich is referenced in the function _mainCRTStartup
fatal error LNK1120: 1 external not solved
it´s me the Dogpound, Any solution to this
Posted: Fri Feb 10, 2006 9:02 am
by hybrid
It is just as Nick said one post before. You will have to make sure that all of your input files (headers, *.lib and *.dll) have the same version. There seems to be a mismatch in your files. When linking with the *.lib file your app is told where to find the entry points for the *.dll file. If the app does not find an entry point (method invocation adress) there it refuses to run.
Posted: Fri Feb 10, 2006 9:50 am
by Nick_Japan
ERROR MESSAGE CANNOT FIND PROCEIDURE ENTRY POINT:?createDevice@irr@@YAPAVirrlichtDevice@14WE_DRIVER_TYPE@video@1@ABV?$dimiension2d@H@core@1@I-N22PAVIEventReceiver@1@PBG@Z in the irrlicht.dll dinamic library
Like I said before, this is a dll / lib / header mismatch. But:
error LNK2019: External symbol_main without being solved to wich is referenced in the function _mainCRTStartup
I remember getting some weird compiler errors with Visual C++ 2005 EE which I got rid of by changing some compiler flags. I think some of them were a load of unresolved externals starting with CRT_Something. Try this:
RClick on your project and choose settings (maybe properties, preferences etc) and then in the compiler options go to c/c++ code generation and fiddle with the options here. I think the one that caused this was 'Allow C++ Exceptions' or 'Buffer Security Check'.