Today’s (May 29, 2014) Developer Skill Sprint by John Thomas (JT) covers how to use C++ packages in your 64-bit Windows applications. From the DocWiki: C++Builder XE6 now supports the production of packages for 64-bit Windows. Previously, C++Builder supported production of packages only for 32-bit Windows. The BCC64 compiler produces .bpl files for Win64. Note that C++Builder does not produce dylibs for the Mac, or packages for the iOS and Android platforms. For these platforms, static libraries can be used.
Why use Packages? Design-time packages simplify the tasks of distributing and installing custom components. Runtime packages, which are optional, offer several advantages over conventional programming. By compiling reused code into a runtime library, you can share it among applications.
Differences between C++ Win32 and Win64 packages:
- For Win64, the compiler exports code elements marked as PACKAGE if they are defined in the current translation unit. For classes, if one non member is defined, the class is exported. If no definition is seen, the compiler will treat the code element as imported. This behavior is different from Win32.
- You must use PACKAGE for both Win32 and Win64, but Win64 exports only if there is a definition present. This requirement applies to variables, functions and classes that are meant to be exposed to consumers of the Package.
This Skill Sprint Replay is available on YouTube at http://youtu.be/fVZDJS85MX0
For a complete list of Developer Skill Sprints - check out the landing page at https://www.embarcadero.com/landing-pages/skill-sprints.
You can register for the Developer Skill Sprint series at http://forms.embarcadero.com/DeveloperSkillSprintsWebinarSeries
To use the tips, tricks and techniques covered in the Developer Skill Sprints, you can download the free RAD Studio XE6 trial.