Building a static library that can be used in debug AND release exe's:

[Guest_imported]

Hi All,
At the company I work at, a co-worker and I have developed a set of standard classes and libraries specific to the data our company operates on. The amount of classes now have grown tremendously. The problem we're having is the following:

Each class is contained in it's own static library. These classes are used mostly in Win32 console applications, although sometimes they must be used in MFC applications. Along with that, we also need to allow the rest of the developers to step into the source when debugging. The problem is, we compile the libraries as Multi-threaded (for MFC support) static debug libraries. Now, if we would like to build release versions of the executables that use these libraries we get all the linker errors about mixing debug and release versions.

I've used other companies static libraries (such as a Pro-C static library) that has absolutely no linker problems whether the .exe we're creating is compiled as debug or release.

My question: How do we build our libraries to do the same. (Have no conflicts whether the executable is built as debug or release).

Thanks in advance.

-Ayc

 

[Cagliostro]

When you compile in release mode, the exe files are put in the projects direcotry in the subdirectory \Release, not in \Debug. As result VC++ search in this directory the lib's, obj's, dll's, not in \Debug. As a result, put the libraries in that directory. John Fill

ivfmd@mail.md