Question

I wrote a class library in C++ and successfully compiled it in Linux with g++ as a shared object, then created a few apps that use it. Now I have to port it to VS2008. I gave all the classes the required __declspec(dllexport) prefixes, then tried to compile it. I get a pile of warnings, which basically have to do with:

1. my custom exception classes, derived from std::runtime_error, which yield:
   “warning C4275: non dll-interface class ‘std::runtime_error’ used as base for dll-interface class ‘cci::FileOperationException'”. How am I supposed to make a standard library class dll-exportable?
2. exception specifications in member functions’ declarations, which cause “warning C4290: C++ exception specification ignored except to indicate a function is not __declspec(nothrow)”. I read somewhere that VS doesn’t support these, and that it does somewhere else. How very confusing.

I read people saying that exporting classes in a DLL is generally a Bad Idea, that there’s a myriad of things that can go wrong, and now I have my head full of concepts like binary incompatibility, dll hell, compiler version mismatches etc, and to be honest I can’t really make heads or tails of it. What is the correct, safe and easy way to create a shared class library in Windows, then?

Thanks.

Answer 1

I maintain a C++ class library that is typically used as DLL on Windows, so it can be done. Regarding your issues:

1. That doesn’t happen in my library. Perhaps you need to be using the /MD and /MDd build options? That way your C++ run-time-library comes from a DLL, too, which is the sort of picky thing VC++ is famous for.

2. Don’t use throw-specs. They are evil. If you feel you must do it anyway, just put something like this in a header file that every module includes before it gets to code that uses throw-specs.

#pragma warning(disable: 4290)