|
-
November 12th, 2006, 09:19 AM
#1
Linking against static library
Hello all,
I have simple Win32 command line project using my own static library which in turns requires third-party static library (the Expat XML parser). I have the solution where all these three projects reside (command line EXE, my static library LIB and expat static library LIB).
Now I have it configured in the way that the EXE project has a reference to the Expat static library and my own static library has no reference.
My question is if it were better to have the reference to Expat static library in my own static library instead of having it in the EXE project. I guess its nonsense to have it in both of the projects.
What is your opinion?
Thank you for your contributions, best regards
Standa.
The sun is the same in the relative way, but you're older
Shorter of breath and one day closer to death
- Roger Waters, 1973
-
November 13th, 2006, 04:28 AM
#2
Re: Linking against static library
I think the static library should be independant instead of referencing other libraries, the exe should keep ref. to libraries which are directly-indirectly used.
Note: if the static library used some other library/DLL then you will need to mention that library in application's liknker list, static library don't keep the list of dependancies.
Regards,
Ramkrishna Pawar
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|