This chapter will explain what has to be done to build installation packages for a target platform, that includes all files needed to operate a device without the need to ship the full Balluff Impact Acquire installation package.

Note

This approach is NOT recommended for various reasons. Potential sources of trouble include:

Version conflicts resulting from the official Impact Acquire installation package from Balluff is installed on a target platform in parallel with a custom, private setup routine.
Each time a new release of the Impact Acquire framework becomes available, a private setup routine might need adjustments well.
When shipping parts of this SDK please make sure to ship or refer to any third party license that might be involved. Details can be found here: Which Shipped File Is Affected By Which License but as these might change over time so must private setup routines.

The latest official installation package can always be found here

When a custom installation package has already been developed, this chapter gives detailed information about changes that might affect this package: Migrating Installers

In case a custom installation package shall be created the following chapters, depending on the target platform will contain additional information: