Link Copied
Hi
Probably require to use file def to inform directive "@.........."
also instruction compiler
-DDLLIMPORT=??? -L ....... (origin lib.a if used as converted process to dll)
About conflict ,normally no relation with Icc lib if correctly patched two side.
Normally can run.
Kind regards
Hi,
old thread, but I want to clearify the answer.
You can't use the classes in the dll. The different mangling is often on purpose
to prevent you from runtime errors. There are other ABI issues like return
value handling, register handling, vtable, exception handling and so on. So, even if
you manage to solve the mangling issue the application wont run as expected.
Alex
Hi Bustaf,
the last link is really interesting. There seems to be a possibility to use a
dll containing C++ code with a different compiler ABI than that which are
created the dll. I hope I will find a little bit of time tomorrow to check
that. It is still on my todo list :-)
The other links are mainly telling you to use a C-style wrapper for this constellation.
Thanks!
Alex
For more complete information about compiler optimizations, see our Optimization Notice.