diff --git a/documentation/ref-manual/ref-devtool-reference.xml b/documentation/ref-manual/ref-devtool-reference.xml index 1764f0196f..90330f1a35 100644 --- a/documentation/ref-manual/ref-devtool-reference.xml +++ b/documentation/ref-manual/ref-devtool-reference.xml @@ -215,6 +215,17 @@ The .bbappend file is created to point to the external source tree. + + + If your recipe has runtime dependencies defined, you must be sure + that these packages exist on the target hardware before attempting + to run your application. + If dependent packages (e.g. libraries) do not exist on the target, + your application, when run, will fail to find those functions. + For more information, see the + "Deploying Your Software on the Target Machine" + section. +
@@ -501,6 +512,40 @@ + + + Some conditions exist that could prevent a deployed application + from behaving as expected. + When both of the following conditions exist, your application has + the potential to not behave correctly when run on the target: + + + You are deploying a new application to the target that + has correctly defined runtime dependencies defined in + recipe you used to build the application. + + + The target does not physically have the packages on which + the application depends installed. + + + If both of these conditions exist, your application will not + behave as expected. + The reason for this misbehavior is because the + devtool deploy-target command does not deploy + the packages (e.g. libraries) on which your new application + depends. + The assumption is that the packages are already on the target. + Consequently, when a runtime call is made in the application + for a dependent function (e.g. a library call), the function + cannot be found. + + + + To be sure you have all the dependencies local to the target, you + need to be sure that the packages are pre-deployed (installed) + on the target before attempting to run your application. +