System Requirements

The following table outlines the system requirements for the Anyware Client SDK for macOS:

Anyware Support Bundler Tool

HP Anyware's support team may request a support file from your system to help troubleshoot and diagnose PCoIP issues.

To create a support file:

PCoIP Session Phases

There are two phases in a PCoIP session:

PCoIP Session-Creation Steps and Actors

The steps indicated below are used and documented in the bundled sample code. Refer to the code for specific function calls, expected return values and error-handling requirements. The example C++ code can be found in the SDK package located here:

PCoIP Core Library Integration

The core library allows an application developer to integrate a PCoIP session directly into an application. The core library facilitates connection to a remote host, decoding PCoIP image data directly into an application supplied frame buffer as well as remoting audio, keyboard and mouse events and supported USB devices.

Passing Customization Parameters to the Session Client

When using the l parameter to automatically pass session information to the session client, you can pass additional session client parameters by enclosing them in double quotes.

What's New in This Release?

Release 24.07 of the Client SDK for macOS includes:

Support for Wacom Movink 13

Support for Wacom Movink 13 tablets has been added to version 24.07 of the Client SDK for macOS. For more details, see Wacom Support.

Manually Bridging USB Devices

If you need to support more than 20 USB devices, or if you expect your users to control which devices can be bridged, they can be manually added by opening the client’s USB Devices menu and enabling them.

The following table contains a brief description of the header files included in the Anyware Client SDK for macOS:

Linking the SDK for macOS

This section includes instructions for linking the SDK libraries with your custom client application:

1. Open a Terminal window and change directory to the root of the mounted SDK disk image.

2. Copy the SDK files to desired location for SDK development, refered to as <sdk_location> below.

   CMake modules location