This topic provides general info on porting legacy apps to Legato.
There's also specific info available to Port Legacy C App.
High-level steps for porting your app to Legato:
executables:
section in .adef
empty (or omit that section entirely).files:
subsection of the bundles: section of the .adef file.processes
: section in the .adef to define processes that should run in the app. .adef
file to create the app bundle (e.g., .wp85 or .wp7 file) to be installed on the target.An app bundle produced like this can be installed exactly the same as any other Legato app bundle.
Detailed info:
Definition Files
Create Apps
Port Legacy C App
Here's a foo.adef
sample (for application foo) with executables bar1 and bar2 needing library lib1. The application name should be the same as the .adef file name:
To bundle everything into an app, run:
where [target] is something like "ar7" or "wp85".
The app bundle file can be installed using the instapp
tool.
faultAction
) can also be set in the .adef files. See Application Definition .adef.This method is necessary if your legacy apps require root privileges or access to system resources like /proc
. It means your app will be ported as a non-sandboxed Legato app.
In the .adef file, turn-off sandboxing:
Copyright (C) Sierra Wireless Inc. Use of this work is subject to license.