LNK2019 when linking against a static library.

[g4j31a5]

Hi, dunno if I should post this in C++ or Windows Programming. But here goes. I've got a problem here that bugs me. I'm trying to link a static library to my dll / dynamic library (which in turn will be linked to my application). But I've got all these LNK2019 errors all over the place. This usually happens when I didn't include a .lib file or the .lib file doesn't have the exported symbols, right? Well, the problem is I did link the correct .lib file and after I read MSDN, I tried using dumpbin with /EXPORTS and /SYMBOLS and guess what, the symbols are there. I'll show you one of the errors:

1>bullet_pal.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall btCollisionShape::getBoundingSphere(class btVector3 &,float &)const " (?getBoundingSphere@btCollisionShape@@UBEXAAVbtVector3@@AAM@Z)

And this is from the dumpbin:

272 00000000 UNDEF  notype ()    External     | ?getBoundingSphere@btCollisionShape@@UBEXAAVbtVector3@@AAN@Z (public: virtual void __thiscall btCollisionShape::getBoundingSphere(class btVector3 &,double &)const )

So, maybe there is another cause for this error. But I can't figure out what it is. Can you guys help me please? I'm so lost right now. Thanks a lot in advance.

EDIT: The title is slightly wrong. Not just LNK2019 but LNK2001 and LNK2019. My Bad... :P

[Elysia]

Well, one glaring problem is that the exported function takes a double, while the function you're calling takes a float?
Otherwise it's pretty hard to say anything, except that you must link against the proper library.

[VirtualAce]

Is any other module or is the main module also attempting to link to the lib that the DLL is linking to? I would guess no since that would cause a duplicate symbol error but I have seen on the odd occasion where this error is the result of double linking and the compiler spitting out the wrong error code.

My guess is though that you are linking incorrectly or have a mismatch between the header version and the actual library source.

[g4j31a5]

@Bubba & Elysia: thanks guys. it was my own stupid mistake afterall. the library has this macro:

# if defined BT_DOUBLE_PRECISION
typedef double btScalar;
#else
typedef float btScalar;
#endif

And the funny thing is, in the library I used the prerpocessor BT_DOUBLE_PRECISION but didn't in the one that it is linked to. My bad. :P

Thanks a lot for the pointers guys. Especially Elysia for telling me the double / float difference. I somehow skipped reading that part.

[VirtualAce]

Glad you got it resolved. Linker errors can be nasty beasts at times.