The following table shows where to find files belonging to the Impact Acquire framework on a target machine where the framework has been installed.

Library	ARMhf	ARM64	x86_64
libBVS_CA-BN.[some letter].so		`"$MVIMPACT_ACQUIRE_DIR/lib/arm64"`	`"$MVIMPACT_ACQUIRE_DIR/lib/x86_64"`
libmvBlueFOX.so.3.5.0	`"$MVIMPACT_ACQUIRE_DIR/lib/armhf"`	`"$MVIMPACT_ACQUIRE_DIR/lib/arm64"`	`"$MVIMPACT_ACQUIRE_DIR/lib/x86_64"`
libmvDeviceManager.so.3.5.0	`"$MVIMPACT_ACQUIRE_DIR/lib/armhf"`	`"$MVIMPACT_ACQUIRE_DIR/lib/arm64"`	`"$MVIMPACT_ACQUIRE_DIR/lib/x86_64"`
libmvGenTLConsumer.so.3.5.0	`"$MVIMPACT_ACQUIRE_DIR/lib/armhf"`	`"$MVIMPACT_ACQUIRE_DIR/lib/arm64"`	`"$MVIMPACT_ACQUIRE_DIR/lib/x86_64"`
libmvGenTLProducer.so.3.5.0	`"$MVIMPACT_ACQUIRE_DIR/lib/armhf"`	`"$MVIMPACT_ACQUIRE_DIR/lib/arm64"`	`"$MVIMPACT_ACQUIRE_DIR/lib/x86_64"`
libmvGenTLProducer.PCIe.so.3.5.0		`"$MVIMPACT_ACQUIRE_DIR/lib/arm64"`	`"$MVIMPACT_ACQUIRE_DIR/lib/x86_64"`
libmvImageProcessing.so.3.5.0	`"$MVIMPACT_ACQUIRE_DIR/lib/armhf"`	`"$MVIMPACT_ACQUIRE_DIR/lib/arm64"`	`"$MVIMPACT_ACQUIRE_DIR/lib/x86_64"`
libmvIMPACT_Acquire.java.so.3.5.0	`"$MVIMPACT_ACQUIRE_DIR/lib/armhf"`	`"$MVIMPACT_ACQUIRE_DIR/lib/arm64"`	`"$MVIMPACT_ACQUIRE_DIR/lib/x86_64"`
libmvPropHandling.so.3.5.0	`"$MVIMPACT_ACQUIRE_DIR/lib/armhf"`	`"$MVIMPACT_ACQUIRE_DIR/lib/arm64"`	`"$MVIMPACT_ACQUIRE_DIR/lib/x86_64"`
libmvVirtualDevice.so.3.5.0	`"$MVIMPACT_ACQUIRE_DIR/lib/armhf"`	`"$MVIMPACT_ACQUIRE_DIR/lib/arm64"`	`"$MVIMPACT_ACQUIRE_DIR/lib/x86_64"`
mvIMPACT_Acquire.jar	`"$MVIMPACT_ACQUIRE_DIR/lib/armhf"`	`"$MVIMPACT_ACQUIRE_DIR/lib/arm64"`	`"$MVIMPACT_ACQUIRE_DIR/lib/x86_64"`
mv.impact.acquire.dll (.NET Standard)	`"$MVIMPACT_ACQUIRE_DIR/LanguageBindings/netstandard2.0"`
mv.impact.acquire.examples.helper.dll (.NET Standard)	`"$MVIMPACT_ACQUIRE_DIR/LanguageBindings/netstandard2.0"`

The version number of the files in the list might differ as this table lists the latest version available.
Various symbolic links might be required on the target system as well pointing from
- libXYZ.so.3 to libXYZ.so.3.5.0
- libXYZ.so to libXYZ.so.3
- mvGenTLProducer.cti to libmvGenTLProducer.so
- mvGenTLProducer.PCIe.cti to libmvGenTLProducer.PCIe.so

Everything related to kernel drivers usually doesn't apply here with the exception of BVS CA-BN devices which come with their own kernel driver. If for any reason the original installation packages shall not be used the corresponding install scripts coming with that packages can be used to reverse engineer what needs to be done. As stated previously this NOT recommended!