The following table contains a brief description of the header files included in the Anyware Client SDK for macOS:
Note: Location of the Header Files
The header files are available at the following locations in the Anyware Client SDK for macOS package:
This section includes instructions for linking the SDK libraries with your custom client application:
Open a Terminal window and change directory to the root of the mounted SDK disk image.
Copy the SDK files to desired location for SDK development, refered to as <sdk_location> below.
CMake modules location
The macOS has elements which are part of the operating system user interface and cannot be modified programmatically, as described in the following sections.
The following run-time limitations are enforced by macOS on the application menu (beside the menu apple icon menu):
The Client SDK for macOS provides developers tools to create a custom Anyware client with a unique user interface and workflow, or to embed a PCoIP session into another program or solution. Clients built with the SDK can connect to remote desktops using Anyware agents or Remote Workstation Cards.
The SDK is provided as part of HP Anyware by special agreement with HP.
Brokered Session Connection
If you are using a brokered session, this is handled by the broker libraries automatically.
Before you can establish a PCoIP session with a host desktop, gather the following host desktop details:
The following are answers to commonly asked questions when contemplating how to develop custom Anyware Clients using the Teradici Anyware Client SDK.
Q: Can I brand the pre-session client with my company logo and colors?
The following PCoIP session features can be customized:
Examples show command-line usage
The layout file format used to customize the session client is an UTF-8 XML text file.
The layout schema is a top-level <pcoip-client-branding/> element with a version
attribute describing the schema version, and containing the required elements
described next:
In order to customize your session client, you must create a client branding package using the HP Custom Branding Package Utility. The HP Custom Branding Package Utility is located in the following location:
To create a custom branding package:
The following section outlines the scope precedence commands between the System Scope and User Scope. If you are updating individual user settings then the user scope locations and parameters can be followed. Due to this order of precedence where by the system scope setting takes precedence over the user scope setting, a change in the user settings may not take effect if the system scope setting has been updated.
System Scope