static libraries problem

Question

5.00/5 (1 vote)

See more:

I have a problem with static libraries. I need to use 2 different versions of the same SDK in one DLL without names collisions. I thought that solution is to make 2 static libs for every version of SDK and then import these libs to DLL. But this solution works strange and I'm not sure why....

simplified situation looks like this:

LIB1 - there is function Add1 which uses things from SDK 1.0

LIB2 - there is function Add2 which uses things from SDK 2.0

DLL- imports LIB1 and LIB2 and there is function Add(float version) which calls Add1 or Add2 - depends on version number in parameter

Compilation process is OK but DLL works only with one version SDK :(

When I debug it I see that program calls Add function from DLL with version 2.0 in parameter. Then Add really calls Add2 - so this is still right. BUT then inside Add2 function it uses things which are defined in SDK 1.0 instead of SDK 2.0 ! LIB2 is really created with SDK 2.0. (include dirs and lib dirs are set to SDK 2.0)

So why it uses SDK 1.0 ??? :(

Is it because of linker which joins everything together when I create DLL and symbols from SDK 1.0 override symbols from SDK 2.0 ??? (SDKs don't have different namespaces).

Do you have any idea where is problem and is there any solution ???

Thanks a lot!

I use Visual C++ 2010...

Posted 8-Oct-11 7:52am

ExeCom

Add a Solution

3 solutions

Solution 3

It certainly looks like LIB2 is wrongly linking to SDK 1.0.
Here is what I would try to do -
Install only SDK 2.0 and build only LIB2.
If this works, we can try to install both SDK 1.0 and 2.0 and build only LIB2.
I believe that this way we could narrow down the cause of the problem.

Posted 9-Oct-11 16:57pm

«_Superman_»

Solution 1

Use GetProcAddress[^] to specify which one to use.

Posted 8-Oct-11 9:16am

PJ Arends

Comments

CPallini 8-Oct-11 16:38pm

AFAIK you cannot use it with a static library's function.

ExeCom 8-Oct-11 16:42pm

GetProcAdress ???????

Add1 and Add2 are in static libs and there isn't any problem with calling them.... There is problem inside them. How do you want to choose SDK with getprocadress ??? SDK is a lot of *.h and *.lib files with declarations and definitions. I don't understand. how do you think it ?

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard MacCutchan · Accepted Answer · 2011-10-08T21:26:00

Solution 2

You will always have a problem with this if there are any names which exist in both LIB1 and LIB2. As suggested above you would be better to make these both DLLs and use LoadLibrary and GetProcAddress to select the correct functions.

Posted 8-Oct-11 21:26pm

Richard MacCutchan

Comments

Guyverthree 10-Oct-11 6:38am

Yes this will solve the problem. + 5