S
Scott Brady Drummonds
Hi, everyone,
I'm working on a software project that contains some C++ code that I would
like to be common to two separate projects. Ideally, I'd like to have each
of these separate projects conditionally compile and link the common code
per environment configuration. However, I feel that the very nature of this
common code (that it is mutually compile- and link-time dependent with the
software projects) precludes this type of setup. As such, I think that the
solution may fall into the realm of programming instead of build environment
configuration.
In an independent discussion I've been having in a build environment mailing
list, someone mentioned that I should investigate a plugin type architecture
for this solution. I believe the implication here is that stub header files
are provided, perhaps in conjunction with dummy libraries, that serve as
interfaces to real libraries that might be statically or dynamically linked
later, or even executed as a separate process. However, I'm not quite
certain.
Can anyone recommend a book, webpage, or example code that would show me how
I can break physical dependencies in logically dependent C++ code? I've
enjoyed some of the techniques in the John Lakos book
(_Large_Scale_C++_Programming_, I belive) but think that I need another
physical-minded C++ design book to help me out.
Thank you for your help!
Scott
I'm working on a software project that contains some C++ code that I would
like to be common to two separate projects. Ideally, I'd like to have each
of these separate projects conditionally compile and link the common code
per environment configuration. However, I feel that the very nature of this
common code (that it is mutually compile- and link-time dependent with the
software projects) precludes this type of setup. As such, I think that the
solution may fall into the realm of programming instead of build environment
configuration.
In an independent discussion I've been having in a build environment mailing
list, someone mentioned that I should investigate a plugin type architecture
for this solution. I believe the implication here is that stub header files
are provided, perhaps in conjunction with dummy libraries, that serve as
interfaces to real libraries that might be statically or dynamically linked
later, or even executed as a separate process. However, I'm not quite
certain.
Can anyone recommend a book, webpage, or example code that would show me how
I can break physical dependencies in logically dependent C++ code? I've
enjoyed some of the techniques in the John Lakos book
(_Large_Scale_C++_Programming_, I belive) but think that I need another
physical-minded C++ design book to help me out.
Thank you for your help!
Scott