When you installed Storyboard all of the supported target configurations were installed to "[install root]/Storyboard Engine". Each directory there contains the plugins and binaries required to run Storyboard on an embedded target. For this example we will assume a Linux ARMLE system using a framebuffer device.
First we must put the plugins and engine onto the target. The files can be copied to the target or remotely mounted. Create a directory on the target for the Engine such as "Storyboard". In a final setup you would only put the plugins your application requires but for this example we will put all plugins on the target. Create 2 new directories and copy the following files from host to target:
[install root]/Storyboard Engine/linux_armle-armle-fbdev-obj/plugins/* -> [target]/Storyboard/plugins
[install root]/Storyboard Engine/linux_armle-armle-fbdev-obj/bin/sbengine -> [tagget]/Storyboard/bin
Now we need an application to run. Samples are shipped in the "[install root]/Samples" directory. Copy one of these to the target system, copy all files in the selected sample as the samples contain all of the images, fonts, scripts and deployment files required. For example copy "button-example" to the target system's "/tmp" directory.
Storyboard loads plugins for added functionality. It loads these based on the environment variable "GRE_PLUGINS". This can be set to a list of plugins or to a directory. For our case lets set it to the plugin directory:
Storyboard for Linux uses Freetype for font loading and rendering so make sure that libfreetype.so is on the target.
Now you can run your application.
Note: If your application uses the Storyboard IO API then make sure that you have configured the Linux kernel for mqueue.