Extensible SDK Debugging: Difference between revisions
From Yocto Project
Jump to navigationJump to search
PaulEggleton (talk | contribs) (Basic info about accessing eSDK internals) |
PaulEggleton (talk | contribs) No edit summary |
||
| Line 10: | Line 10: | ||
. ./layers/<core layer>/oe-init-build-env . | . ./layers/<core layer>/oe-init-build-env . | ||
</pre> | </pre> | ||
'''WARNING:''' don't miss out the " ." at the ''end'' of the last command - if you do, it will not work! | |||
Now you can run bitbake as you would normally. | Now you can run bitbake as you would normally. | ||
Latest revision as of 01:03, 13 December 2016
The extensible SDK is effectively an encapsulated instance of the normal build system. Generally that shouldn't be touched directly, however sometimes you need to debug why it's not doing what you expect it to do, either at install time or runtime.
Accessing the eSDK internals
Run the following commands:
cd /path/to/sdk/install . ./environment-setup-<tab complete> . ./layers/<core layer>/oe-init-build-env .
WARNING: don't miss out the " ." at the end of the last command - if you do, it will not work!
Now you can run bitbake as you would normally.
