I just installed C++ Builder 10 (Seattle) trial but now facing a strange error when trying to compile any (new or existing) VCL Forms application.
It's a clean installation, no settings were modified etc. I'm using Windows 10. How to solve this?
I just installed C++ Builder 10 (Seattle) trial but now facing a strange error when trying to compile any (new or existing) VCL Forms application.
It's a clean installation, no settings were modified etc. I'm using Windows 10. How to solve this?
On
I think I found a solution.
In existing projects built in previous versions of C++ Builder this may cause the following linker errors:
Unresolved external '___seh_personality_v0' Unresolved external '__Unwind_SjLj_Register' Unresolved external '___cxa_begin_catch'
Unresolved external '___cxa_rethrow' Unresolved external '___cxa_end_catch' Unresolved external '__Unwind_SjLj_Unregister'
Unresolved external '__Unwind_Resume' Unresolved external '___cpp_terminate'
To remove those errors go to
$(BDS)\lib\win32\release\'
On
This happened to me when I installed an older version of RAD Studio after a newer version was already installed. In my case I installed XE2 after XE10 was already installed.
In my Windows PATH the directories of the newer version (XE10)
e.g.: C:\Program Files (x86)\Embarcadero\Studio\17.0\bin
were listed after the directories of the older version (XE2)
e.g.: C:\Program Files (x86)\Embarcadero\RAD Studio\9.0\bin
therefore an old version of borlndmm.dll was found instead of the actual one.
So I just moved the newer PATH records in front of the newer ones, restarted RAD Studio and everything was fine. I mean,... as it was before.
This is bug RSP 11768, which I suspect will be fixed in Update 1. See also this forum thread.
There are a number of solutions in that bug report:
__dbk_fcall_wrapperanddbkFCallWrapperAddr; see the bug for details)