It seems to be why they combine, because in the OR SDK has a class for the line – FBString. However, with such a challenge comes when you want to connect third-party libraries or their development, often it’s all tied to the STL string and get rid of that there is no possibility.

OR SDK and STL string together generate 118 errors when compiling from error C2365: ‘operator new’: redefinition; previous definition was ‘function’

It seems that there is no reason to combine them, because in the OR SDK there is a class for the string – FBString. However, such a challenge comes when you want to connect third-party libraries or own development, often it’s all tied to the STL string and get rid of that there is no possibility.

The ways out can be as follows:

  • Especially files,  which are connected to the header OR SDK, separated from the STL files. But the interaction between the code for the OR SDK and code using the STL, you can build on the use of “extern” functions. Moreover, these functions should have a standard data types for C + + (not referring to OR SDK and not touching STL)
  • The second option to withdraw their code using the STL in a separate dynamic library and link it to the MoBu plug, but also without using the STL, but only the standard data types in C + +
  • Well, and the option to replace the STL string to FBString or any other custom string class.
OR SDK and STL string
Tagged on:                 

Leave a Reply

Your email address will not be published. Required fields are marked *