How to create a .dll for clients using either different compilers or different version of the same compiler

Question

0.00/5 (No votes)

See more:

, +

Hi all,
I'm a new member of code project and I'm not an expert software designer, therefore, please, use a simple language for your answers.
Now I'm facing this problem: I have to create a dll which should be used by several clients, using either different compilers or different version of the same compilers (for example Visual Studio 2006 and Visual Studio 2013). My library must contain many class definitions, each of them with its own members and methods. Many class members are std::vector. I want to export only the methods of the main class, you can find the .h of this class (CMsg.h) below:

C++

#include "T_Msg.h"
    
    #ifdef MSG_EXPORTS
    #define MSG_API __declspec(dllexport)
    #else
    #define MSG_API __declspec(dllimport)
    #endif
    
    class MSG_API CMsg
    {
    public:
      CMsg(unsigned char *data, int nLen);
      const std::vector <T_Msg> &ExtractListMsg() {return m_ListMsg;};
    
      CMsg(T_Msg& Msg);
      unsigned char* ExtractBuffer(int& nLen) {nLen = m_WriteBit.LengthByte();return m_WriteBit.DataByte();};
    
      ~CMsg();
    
      void Decode(unsigned char *data, int nLen);
      void Encode(T_Msg& Msg);
    
    private:
    
      std::vector <T_Msg> m_ListMsg;
      CWriteBit m_WriteBit;
    };
    
    #endif // CMsg_H

Can I compile my dll using std::vector as class members and making it portable across different compilers?
Is this the right way? Otherwise, how should I write my classes?
I have found many articles about this problem, but with different suggestions and conclusions (for example for what concerns the use of std::vector). Moreover this articles are often too much complicated and I have a little time to find the right way.
Thank you in advance for your precious answers.

Posted 4-Aug-15 22:46pm

Makhno

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Pascal-78 · Answer 1 · 2015-08-04T23:52:00

I would advise you to avoid standard library in any exported method because even with the same compiler, the debug and release version of a std::vector can be different.

I have write a complex interface for a project inside my company, it must be compatible with Borland C++ 2009 and VS2010.

To manage this project using the following tips :

I create my own template vector to have :
- same allocate memory method (new/delete/malloc/free are not compiler compatible)
- same data structure (std::vector do not have same data members in Borland and VS)
calling convention forced to __stdcall (by default VS uses __thiscall which put the this pointer in the ecx register and not in the stack)
to allow DLL evolution without recompiling the all project, I fixed interface (abstract class without any data members)
avoid structure in return type (Borland and VS filled the returned structure differently)

To your class :

keep any private data private : do not put them in .h file use class inheritance
use basic type to transfert data : to fill (std::vector<t>&) use (T* data, size_t maxItem)

CMsg.h

C++

#include "T_Msg.h"
#ifdef MSG_EXPORTS
#define MSG_API __declspec(dllexport)
#else
#define MSG_API __declspec(dllimport)
#endif
MSG_API IMsg* CreateMsg(unsigned char* data, int nLen);
MSG_API void DeleteMsg(IMsg* msg);
class IMsg
{
protected:
virtual ~IMsg() { }; // will generate error if delete is used on a IMsg*
public:
// All methods are pure virtual (=0)
virtual int __stdcall ExtractListMsg(T_Msg* data, size_t nbMaxItem) = 0;
virtual int __stdcall ExtractBuffer(unsigned char* data, size_t nbMaxLen) = 0;
virtual void __stdcall Decode(unsigned char *data, int nLen) = 0;
virtual void __stdcall Encode(T_Msg& Msg) = 0;
};

CMsg.cpp

C++

...
class CMsg : public IMsg
{
public:
  // Implement the virtual method from IMsg here.
private:
  std::vector<T_Msg> m_ListMsg;
  CWriteBit m_WriteBit;
};
...

I will not write all here, you will have to complete by yourself...