Using RealSense extensions' hooks

What will the hooks do?

• Get required verison of RealSense SDK Runtime web-setup installer by downloading or finding in current packaging directory in which Crosswalk-pkg is triggerred.
• Collect all the modules need to be installed, such as: face3d, scene_perction, epv, etc.
• Embedded the RSSDK runtime in the Web App's installer and set the right installing command line options.
• This hooks only support Windows currently.
• If the hooks run correctly, there are two outputs:

xx.xx.xx-VERSION.msi
xx.xx.xx_with_realsense_runtime-VERSION.msi

The MSI file has no runtime bundled, while the EXE file has the runtime.

How to use it?

• Put the extensions and hooks into Application's root directory.
• Specify the needed extensions in Application's manifest.json file.
• Run crosswalk-pkg to package the Application, for example:

crosswalk-pkg -p windows -c CROSSWALK_BINARY_PATH/CROSSWALK_VERSION/CROSSWALK_RELEASE_CHANNEL APP_ROOT_PATH

Package the hooks into a App

First you need to add the hooks into the extensions' folders in your App. The release package of Crosswalk-realsense-extensions will contains both the extensions and the hooks. You just need to unpack the released package into you Application's root directory and specify each module you need in the Application's manifest.json file. Please refer packaging rules.

Environment variables

• RS_RUNTIME_WEB_INSTALLER

This variable is used to set the local path of the RSSDK runtime installer, for example on Windows:

set RS_RUNTIME_WEB_INSTALLER=C:\work\intel_rs_sdk_runtime_websetup_8.0.24.6528.exe

• NO_RS_RUNTIME_HOOKS

If this variable was set to 1/true, all the actions in the hooks will be skipped and no bundle EXE including RSSDK runtime installer will be generated. This is usful if the runtime was already installed in the system, and we need a quick develop cycle.

set NO_RS_RUNTIME_HOOKS=1
or
set NO_RS_RUNTIME_HOOKS=true