mirror of
git://git.yoctoproject.org/poky.git
synced 2025-07-19 12:59:02 +02:00
3ccb4d8ab1
The new devtool ide plugin provides the eSDK and configures an IDE to
work with the eSDK. In doing so, bitbake should be used to generate the
IDE configuration and update the SDK, but it should no longer play a
role when working on the source code. The work on the source code should
take place exclusively with the IDE, which, for example, calls cmake
directly to compile the code and execute the unit tests from the IDE.
The plugin works for recipes inheriting the cmake or the meson bbclass.
Support for more programming languages and build tools may be added in
the future.
There are various IDEs that can be used for the development of embedded
Linux applications. Therefore, devtool ide-sdk, like devtool itself,
supports plugins to support IDEs.
VSCode is the default IDE for this first implementation. Additionally,
some generic helper scripts can be generated with --ide none instead of
a specific IDE configuration. This can be used for any IDE that
supports calling some scripts.
There are two different modes supported:
- devtool modify mode (default):
devtool ide-sdk configures the IDE to manage the build-tool used by the
recipe (e.g. cmake or meson). The workflow looks like:
$ devtool modify a-recipe
$ devtool ide-sdk a-recipe a-image
$ code "$BUILDDIR/workspace/sources/a-recipe"
Work in VSCode, after installing the proposed plugins
Deploying the artifacts to the target device and running a remote
debugging session is supported as well.
This first implementation still calls bitbake and devtool to copy the
binary artifacts to the target device. In contrast to compiling,
installation and copying must be performed with the file rights of the
target device. The pseudo tool must be used for this. Therefore
bitbake -c install a-recipe && devtool deploy-target a-recipe
are called by the IDE for the deployment. This might be improved later
on.
Executing the unit tests out of the IDE is supported via Qemu user if
the build tool supports that. CMake (if cmake-qemu.bbclass is
inherited) and Meson support Qemu usermode.
- Shared sysroots mode: bootstraps the eSDK with shared sysroots for
all the recipes passed to devtool ide-sdk. This is basically a wrapper
for bitbake meta-ide-support && bitbake build-sysroots. The workflow
looks like:
$ devtool ide-sdk --share-sysroots a-recipe another-recipe
vscode where/the/sources/are
If the IDE and the build tool support it, the IDE gets configured to
offer the cross tool-chain provided by the eSDK. In case of VSCode and
cmake a cmake-kit is generated. This offers to use the cross
tool-chain from the UI of the IDE.
Many thanks to Enguerrand de Ribaucourt for testing and bug fixing.
(From OE-Core rev: 3f8af7a36589cd05fd07d16cbdd03d6b3dff1f82)
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
||
|---|---|---|
| .. | ||
| contrib | ||
| cross-intercept | ||
| esdk-tools | ||
| lib | ||
| native-intercept | ||
| nativesdk-intercept | ||
| postinst-intercepts | ||
| pybootchartgui | ||
| tiny | ||
| autobuilder-worker-prereq-tests | ||
| bblock | ||
| bitbake-prserv-tool | ||
| buildall-qemu | ||
| buildhistory-collect-srcrevs | ||
| buildhistory-diff | ||
| buildstats-diff | ||
| buildstats-summary | ||
| combo-layer | ||
| combo-layer-hook-default.sh | ||
| combo-layer.conf.example | ||
| cp-noerror | ||
| create-pull-request | ||
| crosstap | ||
| devtool | ||
| gen-lockedsig-cache | ||
| gen-site-config | ||
| git | ||
| install-buildtools | ||
| multilib_header_wrapper.h | ||
| oe-build-perf-report | ||
| oe-build-perf-test | ||
| oe-buildenv-internal | ||
| oe-check-sstate | ||
| oe-debuginfod | ||
| oe-depends-dot | ||
| oe-find-native-sysroot | ||
| oe-git-archive | ||
| oe-git-proxy | ||
| oe-gnome-terminal-phonehome | ||
| oe-pkgdata-browser | ||
| oe-pkgdata-browser.glade | ||
| oe-pkgdata-util | ||
| oe-publish-sdk | ||
| oe-pylint | ||
| oe-run-native | ||
| oe-selftest | ||
| oe-setup-builddir | ||
| oe-setup-layers | ||
| oe-test | ||
| oe-time-dd-test.sh | ||
| oe-trim-schemas | ||
| oepydevshell-internal.py | ||
| opkg-query-helper.py | ||
| patchtest | ||
| patchtest-get-branch | ||
| patchtest-get-series | ||
| patchtest-send-results | ||
| patchtest-setup-sharedir | ||
| patchtest.README | ||
| pythondeps | ||
| README | ||
| recipetool | ||
| relocate_sdk.py | ||
| resulttool | ||
| rootfs_rpm-extract-postinst.awk | ||
| rpm2cpio.sh | ||
| runqemu | ||
| runqemu-addptable2image | ||
| runqemu-export-rootfs | ||
| runqemu-extract-sdk | ||
| runqemu-gen-tapdevs | ||
| runqemu-ifdown | ||
| runqemu-ifup | ||
| runqemu.README | ||
| send-error-report | ||
| send-pull-request | ||
| sstate-cache-management.py | ||
| sstate-diff-machines.sh | ||
| sstate-sysroot-cruft.sh | ||
| sysroot-relativelinks.py | ||
| task-time | ||
| test-reexec | ||
| test-remote-image | ||
| verify-bashisms | ||
| wic | ||
| yocto_testresults_query.py | ||
| yocto-check-layer | ||
| yocto-check-layer-wrapper | ||
This directory contains Various useful scripts for working with OE builds