unresolved external
-
- Posts: 11
- Joined: Sat Mar 14, 2009 3:40 pm
unresolved external
hi.
I have to compile and run irrlicht from C++ builder 6.
when I try to compile helloword example I receive this error :
[Linker Error] Unresolved external 'irr::createDevice(irr::video::E_DRIVER_TYPE, const irr::core::dimension2d<int>&, unsigned int, bool, bool, bool, irr::IEventReceiver *, const char *)' referenced from F:\VISUALIZER\IRRLICHT-1.4\EXAMPLES\01.HELLOWORLD\MAIN.OBJ
How can I fix this error ?
I have to compile and run irrlicht from C++ builder 6.
when I try to compile helloword example I receive this error :
[Linker Error] Unresolved external 'irr::createDevice(irr::video::E_DRIVER_TYPE, const irr::core::dimension2d<int>&, unsigned int, bool, bool, bool, irr::IEventReceiver *, const char *)' referenced from F:\VISUALIZER\IRRLICHT-1.4\EXAMPLES\01.HELLOWORLD\MAIN.OBJ
How can I fix this error ?
-
- Posts: 11
- Joined: Sat Mar 14, 2009 3:40 pm
I'm not certain, but it is quite possible that you're linking the wrong Irrlicht library (you most likely need to link to the .lib file) or you're not linking to the Irrlicht library at all. If that is not the case I'd guess that there is some link incompatibility between the Irrlicht library you're trying to link to and the object code that you've created (not incredibly likely, but I'm not familiar with the Borland compiler).
I know that the dumpbin tool that ships with the Microsoft compiler can be used to get a list of exports from a library and dependencies of an object file. You could use a tool like this to ensure that the object code you've generated is trying to locate the same symbols that are defined in the Irrlicht library.
Travis
I know that the dumpbin tool that ships with the Microsoft compiler can be used to get a list of exports from a library and dependencies of an object file. You could use a tool like this to ensure that the object code you've generated is trying to locate the same symbols that are defined in the Irrlicht library.
Travis
-
- Posts: 11
- Joined: Sat Mar 14, 2009 3:40 pm
it's definitely a linking problem.
did you include the path to irrlicht.lib in the compiler options?
you could try #pragma comment(lib,"Irrlicht.lib") if you haven't already
did you include the path to irrlicht.lib in the compiler options?
you could try #pragma comment(lib,"Irrlicht.lib") if you haven't already
One Tequila, Two Tequila, Three Tequila, Floor.
_______________________________________
ASUS P5V-VM Ultra
Intel Pentium D930
1x 2GB DDR2 Kingmax 800mhz/533mhz mb
Leadtek PX9600GT W 512MB DDR3
200GB Maxtor HDD
_______________________________________
ASUS P5V-VM Ultra
Intel Pentium D930
1x 2GB DDR2 Kingmax 800mhz/533mhz mb
Leadtek PX9600GT W 512MB DDR3
200GB Maxtor HDD
-
- Posts: 11
- Joined: Sat Mar 14, 2009 3:40 pm
You don't include a lib file, you link it, but I'm assuming that is just your misuse of the terminology.
If your linker is indeed finding the lib file, but it does not see the exported symbol, then there is some incompatibility between the pre-built Irrlicht library and the generated object code. I believe that the easy way to fix this is to build the Irrlicht library with the Borland compiler, but I don't know how much work that would be considering that it isn't one of the supported configurations.
Travis
If your linker is indeed finding the lib file, but it does not see the exported symbol, then there is some incompatibility between the pre-built Irrlicht library and the generated object code. I believe that the easy way to fix this is to build the Irrlicht library with the Borland compiler, but I don't know how much work that would be considering that it isn't one of the supported configurations.
Travis
-
- Posts: 11
- Joined: Sat Mar 14, 2009 3:40 pm
-
- Posts: 11
- Joined: Sat Mar 14, 2009 3:40 pm