DLL's that depend on each other
- From: Russ <russk2t@xxxxxxxxxxx>
- Date: Wed, 20 May 2009 09:30:44 -0400
Hi all. I have a large DLL that I thought was becoming unwieldy and I
decided to try splitting it into two separate libraries. I picked a
set of files that relate to one aspect of the operations and created a
new library using just them. This resulted in reducing the size of
the original library by 1/3 and was quite satisfactory. The original
library is my 'main' DLL and it does not depend on any other library
(other than system libs). The new lib was set to depend on the
original and that worked nicely.
However when I went back and removed the moved files from the original
lib, there were a lot of unresolved references. Now comes the
problem. I cannot set the original lib to depend on the new one
because it creates a circular dependency. Understandable. So I got
around that by just adding the new library to the linker input. Well
that compiles and works, but it also creates a circular dependency in
that every time I rebuild my project the two libraries are both
relinked and so is every other project in the solution that depends
upon them.
This is clearly unnaceptable, so what can I do. Am I forced in this
situation to put the libraries back into one to eliminate this cross
dependency, or is there some other way to handle this? I have already
examined the code and determined that there is no way to split the
library in any usable way that would not result in the cross
dependency.
Thanks, Russ
.
- Follow-Ups:
- Re: DLL's that depend on each other
- From: Scot T Brennecke
- Re: DLL's that depend on each other
- Prev by Date: How to chat using voice?
- Next by Date: ShowWindow(SW_NOACTIVATE) in CDialog Application
- Previous by thread: How to chat using voice?
- Next by thread: Re: DLL's that depend on each other
- Index(es):
Relevant Pages
|