You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Windows setup is genereated from a Release build. Thus, the setup only contains release binaries. When linking against the eCAL Setup in a debug build, you will end up with a mixed debug/release binary. As the C++ Debug ABI and C++ Release ABI are not compatible, the applications will crash when trying to pass STL containers to eCAL:
Linking against the C interface (eCAL::core_c) seems to work in a debug build. I however doubt that it is possible to produce a working debug binary with that workaround, once you use protobuf.
We therefore have to also ship the Debug built along in the Windows installer.
The Windows setup is genereated from a Release build. Thus, the setup only contains release binaries. When linking against the eCAL Setup in a debug build, you will end up with a mixed debug/release binary. As the C++ Debug ABI and C++ Release ABI are not compatible, the applications will crash when trying to pass STL containers to eCAL:
Linking against the C interface (eCAL::core_c) seems to work in a debug build. I however doubt that it is possible to produce a working debug binary with that workaround, once you use protobuf.
We therefore have to also ship the Debug built along in the Windows installer.
Also see #79
The text was updated successfully, but these errors were encountered: