Release Notes for XE3 Update 2
XE3 Update 2 includes:
- C++Builder XE3 Update 1 (64-Bit Windows)
- Help Update 3 for Delphi and C++Builder XE3
This file contains important supplementary information that might not appear in the main product documentation. Embarcadero Technologies recommends that you read this file in its entirety.
This document refers to "the product" when the information applies to RAD Studio XE3 or to either or both of the two personalities: Delphi XE3 and C++Builder XE3.
For general information about installation, deployment, and licensing, see the Install, Deploy, and License files located, by default, at C:\Program Files\Embarcadero\RAD Studio\10.0.
Obtaining this Update
Delphi and C++Builder XE3 Update 2 is an MSI product installer that includes installers for the Platform Assistant, for the online help (XE3 Help Update 3), for Boost, and for other third party products. For instructions for installing the update, see Contents of Update 2 and Instructions for Installation.
This update applies to the following products:
- Delphi XE3
- C++Builder XE3
- RAD Studio XE3
You can obtain this update by Downloading from the Registered Users Web Page.
Downloading from the Registered Users Web Page
Update 2 is available for download from the registered users download pages as follows:
- Delphi XE3: http://cc.embarcadero.com/reg/delphi
- C++Builder XE3: http://cc.embarcadero.com/reg/c_builder
- RAD Studio XE3: http://cc.embarcadero.com/reg/rad_studio
Download <delphicbuilder_xe3_upd2.exe> to your computer. This is the installer that installs XE3 Update 2. The steps to follow for installation are in #Installing XE3 Update 2.
If you have a previous version of XE3 installed, you should uninstall it using the directions in #Uninstalling XE3 Update 1.
Uninstalling This Update
If you need to uninstall the update, you must uninstall the entire product and reinstall the XE3 Update 1 inline build. It is not possible to uninstall only the update.
Contents of XE3 Update 2 and Instructions for Installation
Uninstalling XE3 Update 1
If you have installed any of the XE3 products listed in #Obtaining this Update, you must uninstall the XE3 product before installing XE3 Update 2.
- In the Control Panel, select the option for uninstalling an application.
- Select your installed XE3 product and start the uninstall process.
Installing XE3 Update 2
- To start the installation, run the downloaded <delphicbuilder_xe3_upd2.exe> installer.
- Open your obtained Update 2. The update is immediately extracted to your %TEMP% folder.
- When Windows Explorer appears, run setup.exe.
Installing the Platform Assistant Update
XE3 Update 2 contains updated Platform Assistant files (including PAserver.exe and PAServer.zip). The Update 2 installer does not install these files for you. These files are located in your XE3 Update 2 install folder inside the PAServer folder.
To uninstall the Platform Assistant:
- On Windows, use Uninstall PAServer.exe to uninstall the Platform Assistant.
- On the Mac, use the Uninstall command to uninstall the Platform Assistant.
- Note: The Uninstall programs are located in the installation directory for the Platform Assistant on the PC and on the Mac.
To install the updated Platform Assistant:
- On Windows, double-click PAServer.exe.
- On the Mac, move the PAServer.zip file to the Mac and double-click PAServer.zip.
For more information, see Installing and Running the Platform Assistant (paserver) on the Target Platform.
Bug List for XE3 Update 2
For a complete list of the specific problems fixed in this update, see "Bug Fixes in Delphi and C++Builder XE3 Update 2": http://edn.embarcadero.com/article/42863
C++ OS X Applications Require Xcode Command Line Tools Installed
C++ applications that have the target platform OS X might fail to compile, and you might see compiler error E2209 Unable to open include file 'filename' (C++). A suggested workaround is to ensure that the Xcode command line tools are installed on the Mac. To do this: Open Xcode on the Mac, choose Xcode/Preferences/Downloads and ensure that "Command line tools" shows "Installed". Also, in the IDE, choose the SDK that matches your OS X version (in the Select SDK Version dialog box).
Disconnected Debugger Session Might Occur if Breakpoint is Assigned to a Thread
If you set a breakpoint and associate the breakpoint with a thread (using the Breakpoint properties dialog box), when you run the application in debug mode, the debugger might disconnect after several successful Step Over commands. For information about the Thread property, see Add Address Breakpoint or Add Data Breakpoint.
Two Exception Notifications Occur When Throwing a Delphi Object from C++
If you throw a Delphi exception from C++ code, you might see two separate exception notification dialog boxes.
This happens because first the C++ RTL notifies the debugger of the throw from C++, and then it notifies the debugger of the second exception after it determines this is a Delphi exception. You can ignore the first of these exceptions just by clicking Continue.
If you want to cause the debugger to stop only on the Delphi exception notification, select Ignore this exception type on the Debugger Exception Notification dialog box, but this will prevent the debugger from being able to stop on other C++ exceptions.
typeid.name() Return Mangling Is Implementation-Defined
The string returned by
typeid.name() is implementation-defined. Clang (and therefore BCC64) returns the mangled name of the underlying type. Therefore if the underlying type is
i is returned because that is how an
int is mangled by BCC64. However, BCC32 returns the non-mangled named, which is
int instead of
i. Also see typeid.
- Installation Notes for XE3
- Release Notes for XE3
- Readme - Help Update 1 for Delphi and C++Builder XE3
- Readme - Help Update 2 for Delphi and C++Builder XE3
- Readme - Help Update 3 for Delphi and C++Builder XE3
Copyright 2013 Embarcadero Technologies. All rights reserved.