How to Install

This article describes how to install the Wireless Communication Library and start using it with your IDE. You can download each WCL framework as an executable installer or as a 7Zip archive. To unzip the 7Zip archived framework, use 7-ZIP If you are having any problems or have any questions about installing framework, please do not hesitate to contact us.

The Wireless Communication Libraty 8 does not require any installation.

• Installing from executable installer
• Installing from 7Zip archive

Registered Version

Before installing a registered version of the framework, make sure you completely uninstalled a demo version. If you use .NET Edition, make sure you delete all the framework assemblies completely. Visual Studio usually copies third-party assemblies into a project's build folder. And even after installing a registered version and running your project, it may still use a demo version. Before using a registered version, make sure you clear your project's build folder.

.NET Assemblies

If you downloaded a demo EXE or registered version of the Wireless Communication Library framework, you have to unpack it first. We use a standard ZIP archive for this so it can be unpacked by standard Windows Explorer. Once you get the framework's executable installer file (EXE file), simply run it and follow the installation instructions.

Unpack Executable Installer

However, there can be a situation when you can not (or do not want) to use an executable installer for any reason. And you need to install the registered version of the framework, which is redistributed as an executable installer only. In this case you can unpack the installer and get the framework's files. The executable installer is built using Inno Setup, so to unpack it, simply use Inno Unpacker.

To unpack the framework executable installer with Inno Unpacker, use one of the commands below:

• Demo version: innounp framework_installer_name -x
• Registered version: innounp framework_installer_name -x -pPWD

where framework_installer_name is the executable installer name; PWD is the password for the registered framework.

When the command completes, you will find a folder named as "{app}" and all the framework's files inside this folder. If you unpacked the 7Zip-archived framework, you simply get the framework's files. After that, refer to the Installing Framework from 7Zip Archive part.

If you already have any previous installation of the framework or you already have any other copy of our framework, just copy the unpacked files into the same folder where the previous version or other framework is located with overriding existing files.

At this step you have the framework ready for installation into your IDE. The framework package contains the following directories:

• Demo - the framework's sample projects (applications);
• Doc - the framework's off-line documentation;
• Lib - the framework's binaries. May contains different files and directories depending on the framework's edition (.NET, C++, VCL);
• Source - the framework's source code (not available in .NET Edition except .NET Edition with source code).

• Install .NET Edition
• Install C++ Edition
• Install VCL Edition

Any .NET Edition does not require any additional installation steps. You can simply open sample projects (solutions) and start using them. To use the .NET Edition in your application, you need to reference the framework's DLL files located in the Lib folder of the framework package.

Any C++ edition does not require any additional installation steps. You can simply open sample projects (solutions) and start using them. To use the C++ Edition in your application, you need to add the framework's libraries into your project. You can use the #pragma directive or your IDE linker options to provide the required framework's libraries. The framework's library files are located in the Lib folder (sorted by the Visual Studio versions). The framework's header files are located in the Source folder.

By default, all C++ editions are built as static libraries with the /MT option. If you need other build configurations, please contact us, and we will try (if possible) to provide libraries with required build options for testing purposes. In this case we also recommend purchasing the framework version with source code so you can change its build configuration as you need.

Installing the VCL edition requires some additional steps. The first thing you have to do is copy some BPL files. Open the Lib folder. You can see a tree or two folders there: Common, Communication (not included with the Wi-Fi Framework), and your framework folder (if you use the Bluetooth Framework, the folder name is Bluetooth; for the Wi-Fi Framework it is WiFi; for the Serial Framework it is Serial).

• Copy files
• Install components
• Add paths

Copy files

Start from the Common folder. Open it and find the folder that corresponds to your Delphi (RAD Studio) version. If you use any Delphi (RAD Studio) below XE (RAD Studio XE), then simply copy wclCommon.bpl into your RAD's Bin folder (it is usually located in c:\Program Files(x86)\{studio_dir}\Bin). For example, for RAD Studio XE, the full path is c:\Program Files (x86)\Embarcadero\RAD Studio\8.0\bin. For RAD Studios starting from XE2, you will find 2 sub-folders: Win32 and Win64. Copy wclCommon.bpl from the Win32 folder to your Studio's Bin folder and copy wclCommon.bpl from the Win64 folder to your Studio's Bin64 folder.

Do the same for the Communication folder (the package name is wclCommunication.bpl) and for your framework's folder (Bluetooth: wclBluetoothFramewoprkR.bpl, Serial: wclSerialFrameworkR.bpl, and WiFi: wclWiFiFrameworkR.bpl).

If you use the Bluetooth or the Wi-Fi framework, you also need to copy files from the DRI folder (the package name is wclDri.bpl).

Install components

Now you need to install the framework's design time package (components).

• If you are installing a framework on RAD Studio XE or below, the design-time package is located in the {app_folder}\Lib\_framework_name_\_ide_ver_ directory.
• If you are installing Framework on RAD Studio XE2 or above, the design time package is located in the {app_folder}\Lib\_framework_name_\_ide_ver_\Win32 directory.

Where {app_folder} is the folder where you unpacked the framework's package, _framework_name_ is the framework name (Bluetooth for the Bluetooth Framework, Serial for the Serial Framework, and WiFi for the Wi-Fi Framework), and _ide_ver_ is your IDE version as described above.

The design time package name is:

• Bluetooth Framework - wclBluetoothFrameworkD.bpl.
• Serial Framework - wclSerialFrameworkD.bpl.
• Wi-Fi Framework - wclWiFiFrameworkD.bpl.

Open the Install Packages dialog (Component->Install Packages), click the Add... button, navigate to the runtime package folder, and select the desired runtime package.

Add paths

The next step is to add paths to the framework's binaries. The binaries are located in the following folders (under the library folder, let's say under the Common, Communication, DRI, Bluetooth, Serial, or WiFi folder):

• CBuilder 6: C6
• Delphi 6: D6
• Delphi 7: D7
• Delphi 2005: D2005
• Developer Studio 2006: D2006
• RAD Studio 2007: D2007
• RAD Studio 2009: D2009
• RAD Studio 2010: D2010
• RAD Studio XE: DXE
• RAD Studio XE2: DXE2
• RAD Studio XE3: DXE3
• RAD Studio XE4: DXE4
• RAD Studio XE5: DXE5
• RAD Studio XE6: DXE6
• RAD Studio XE7: DXE7
• RAD Studio XE8: DXE8
• RAD Studio 10 Seattle: D10
• RAD Studio 10.1 Berlin: D101
• RAD Studio 10.2 Tokyo: D102
• RAD Studio 10.3 Rio: D103
• RAD Studio 10.4 Sydney: D104
• RAD Studio 11 Alexandria: D11
• RAD Studio 12 Athens: D12
• RAD Studio 13 Florence: D13

Starting from RAD Studio XE2, there are two subfolders under the IDE folder: Win32 and Win64.

• Bluetooth Framework Paths
• Serial Frameworks Paths
• Wi-Fi Framework Paths

The {app_folder} is the folder where you unpacked the framework's package.
The _framework_name_ is the framework name (Serial for the Serial Framework; Bluetooth for the Bluetooth Framework; WiFi for the Wi-Fi Framework).
The _ide_ver_ is your IDE version as described above.

Bluetooth Framework

RAD Studio XE or below

• {app_folder}\Lib\Common\_ide_ver_
• {app_folder}\Lib\Communication\_ide_ver_
• {app_folder}\Lib\DRI\_ide_ver_
• {app_folder}\Lib\Bluetooth\_ide_ver_

RAD Studio XE2 or above

• {app_folder}\Lib\Common\_ide_ver_\Win32
• {app_folder}\Lib\Common\_ide_ver_\Win64
• {app_folder}\Lib\Communication\_ide_ver_\Win32
• {app_folder}\Lib\Communication\_ide_ver_\Win64
• {app_folder}\Lib\DRI\_ide_ver_\Win32
• {app_folder}\Lib\DRI\_ide_ver_\Win64
• {app_folder}\Lib\Bluetooth\_ide_ver_\Win32
• {app_folder}\Lib\Bluetooth\_ide_ver_\Win64

Serial Frameworks

RAD Studio XE or below

• {app_folder}\Lib\Common\_ide_ver_
• {app_folder}\Lib\Communication\_ide_ver_
• {app_folder}\Lib\_framework_name_\_ide_ver_

RAD Studio XE2 or above

• {app_folder}\Lib\Common\_ide_ver_\Win32
• {app_folder}\Lib\Common\_ide_ver_\Win64
• {app_folder}\Lib\Communication\_ide_ver_\Win32
• {app_folder}\Lib\Communication\_ide_ver_\Win64
• {app_folder}\Lib\_framework_name_\_ide_ver_\Win32
• {app_folder}\Lib\_framework_name_\_ide_ver_\Win64

Wi-Fi Framework

RAD Studio XE or below

• {app_folder}\Lib\Common\_ide_ver_
• {app_folder}\Lib\DRI\_ide_ver_
• {app_folder}\Lib\WiFi\_ide_ver_

RAD Studio XE2 or above

• {app_folder}\Lib\Common\_ide_ver_\Win32
• {app_folder}\Lib\Common\_ide_ver_\Win64
• {app_folder}\Lib\DRI\_ide_ver_\Win32
• {app_folder}\Lib\DRI\_ide_ver_\Win64
• {app_folder}\Lib\WiFi\_ide_ver_\Win32
• {app_folder}\Lib\WiFi\_ide_ver_\Win64

How to add path

• CBuilder 6
• Delphi 6
• Delphi 7
• Delphi 2005
• RAD Studio 2006
• RAD Studio 2007
• RAD Studio 2009
• RAD Studio 2010
• RAD Studio XE
• RAD Studio XE2
• RAD Studio XE3
• RAD Studio XE4
• RAD Studio XE5
• RAD Studio XE6
• RAD Studio XE7
• RAD Studio XE8
• RAD Studio 10 Seattle
• RAD Studio 10.1 Berlin
• RAD Studio 10.2 Tokyo
• RAD Studio 10.3 Rio
• RAD Studio 10.4 Sydney
• RAD Studio 11 Alexandria
• RAD Studio 12 Athens
• RAD Studio 13 Florence

CBuilder 6

You do not need to add any path into the IDE.

Delphi 6, 7

1. Open Environment Options dialog (Tools->Environment Options).
2. Switch to the Library tab.
3. Add paths to the Library path.
4. Click OK to save changes.

Delphi 2005, Developer Studio 2006

1. Open Options dialog (Tools->Options).
2. Expand Environment Options.
3. Expand Delphi Options.
4. Select Library - Win32.
5. Add paths to the Library path.
6. Click OK to save changes.

RAD Studio 2007, 2009, 2010

1. Open Options dialog (Tools->Options).
2. Expand Environment Options.
3. Expand Delphi Options.
4. Select Library - Win32.
5. Add paths to the Library path.
6. Expand C++ Options.
7. Select Path and Directories.
8. Add paths to the Include Path.
9. Add paths to the Library Path.
10. Click OK to save changes.

RAD Studio XE

1. Open Options dialog (Tools->Options).
2. Expand Environment Options.
3. Expand Delphi Options.
4. Select Library.
5. Add paths to the Library path.
6. Expand C++ Options.
7. Select Path and Directories.
8. Add paths to the Include Path.
9. Add paths to the Library Path.
10. Click OK to save changes.

RAD Studio XE 2

1. Open Options dialog (Tools->Options).
2. Expand Environment Options.
3. Expand Delphi Options.
4. Select Library.
5. Select 32-bit Windows from the Selected Platform drop down box.
6. Add Win32 paths to the Library path.
7. Select 64-bit Windows from the Selected Platform drop down box.
8. Add Win64 paths to the Library path.
9. Expand C++ Options.
10. Select Path and Directories.
11. Select 32-bit Windows from the Selected Platform drop down box.
12. Add Win32 paths to the Include Path.
13. Add Win32 paths to the Library Path.
14. Click OK to save changes.

RAD Studio XE 3, 4, 5, 6, 7, 8

1. Open Options dialog (Tools->Options).
2. Expand Environment Options.
3. Expand Delphi Options.
4. Select Library.
5. Select 32-bit Windows from the Selected Platform drop down box.
6. Add Win32 paths to the Library path.
7. Select 64-bit Windows from the Selected Platform drop down box.
8. Add Win64 paths to the Library path.
9. Expand C++ Options.
10. Select Path and Directories.
11. Select 32-bit Windows from the Selected Platform drop down box.
12. Add Win32 paths to the System Include Path.
13. Add Win32 paths to the Library Path.
14. Select 64-bit Windows from the Selected Platform drop down box.
15. Add Win64 paths to the User include Path.
16. Add Win64 paths to the Library Path.
17. Click OK to save changes.

RAD Studio 10 Seattle, 10.1 Berlin, 10.2 Tokyo

1. Open Options dialog (Tools->Options).
2. Expand Environment Options.
3. Expand Delphi Options.
4. Select Library.
5. Select 32-bit Windows from the Selected Platform drop down box.
6. Add Win32 paths to the Library path.
7. Select 64-bit Windows from the Selected Platform drop down box.
8. Add Win64 paths to the Library path.
9. Expand C++ Options.
10. Select Path and Directories.
11. Select 32-bit Windows from the Selected Platform drop down box.
12. Switch to Classic Compiler tab.
13. Add Win32 paths to the System Include Path.
14. Add Win32 paths to the Library Path.
15. Select 64-bit Windows from the Selected Platform drop down box.
16. Add Win64 paths to the User include Path.
17. Add Win64 paths to the Library Path.
18. Click OK to save changes.

RAD Studio 10.3 Rio, 10.4 Sydney, 11 Alexandria, 12 Athens, 13 Florence

1. Open Options dialog (Tools->Options).
2. Expand Language.
3. Expand Delphi Options.
4. Select Library.
5. Select 32-bit Windows from the Selected Platform drop down box.
6. Add Win32 paths to the Library path.
7. Select 64-bit Windows from the Selected Platform drop down box.
8. Add Win64 paths to the Library path.
9. Expand C++ Options.
10. Select Path and Directories.
11. Select 32-bit Windows from the Selected Platform drop down box.
12. Switch to Classic Compiler tab.
13. Add Win32 paths to the System Include Path.
14. Add Win32 paths to the Library Path.
15. Select 64-bit Windows from the Selected Platform drop down box.
16. Add Win64 paths to the User include Path.
17. Add Win64 paths to the Library Path.
18. Click OK to save changes.

That's all! Now you can run Framework's demo apps or start developing your own. Should you have any questions, please do not hesitate to contact us.