-
Notifications
You must be signed in to change notification settings - Fork 247
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: yoctoproject/poky
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: savoirfairelinux/poky-ide
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: staging
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
Can’t automatically merge.
Don’t worry, you can still create the pull request.
- 9 commits
- 20 files changed
- 1 contributor
Commits on Sep 27, 2023
-
vscode: add minimal configuration
It is essential to configure VSCode indexer plugins to ignore the build folder of bitbake. Otherwise, the indexer plugins run with 100% CPU load until an OOM exception occurs. In practice, this makes VSCode more or less unusable for working with Yocto until a file like the one added by this commit is deployed before VSCode starts. From the user's point of view, it is not obvious why the system runs at 100% CPU load and eventually crashes. It is even more misleading that VSCode starts the indexers immediately, but does not stop or reconfigure them when the ignore list is updated. In practice, this means that every time the ignore list is changed, VSCode immediately starts indexing the build folder until the OOM exception stops it. Depending on the system's OOM handler, the entire build machine may crash. Particularly annoying is the Python plugin that ignores the general ignore list and requires an extra ignore section. The settings are suitable for workflows like bitbake, devtool modify, devtool reset. The settings are not intended to work on the source code of a recipe. It is assumed that a separate instance of VSCode is used per workspace folder. These per workspace instances can have different settings depending on the details of the sources that come with the recipe. The new devtool ide plugin will generate settings to match this. Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Configuration menu - View commit details
-
Copy full SHA for 2a86303 - Browse repository at this point
Copy the full SHA 2a86303View commit details -
Define the CMAKE_CROSSCOMPILING_EMULATOR variable similar to what the meson bbclass does. This allows for example to execute cross compilied unit tests on the build machine. CMAKE_CROSSCOMPILING_EMULATOR is a semi colon separated list of paramters which could directly handle the -L and the -E parameters. Creating a wrapper script is not absolutely mandatory. But anyway lets do it similar to what the meson.bbclass does and also disable pseudo. Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Configuration menu - View commit details
-
Copy full SHA for 034dc95 - Browse repository at this point
Copy the full SHA 034dc95View commit details -
The new devtool ide plugin configures an IDE to work with the eSDK. With this initial implementation VSCode is the default 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. Using the plugin in recipe modes: $ devtool modify a-recipe $ devtool ide a-recipe a-image $ code "$BUILDDIR/workspace/sources/a-recipe" Work in VSCode, after installing the proposed plugins Using the plugin without a recipe $ devtool ide none a-image vscode where/the/sources/are Use the cross tool-chain which is provided as a cmake-kit. The goal of this implementation is to create a configuration for VSCode (or other IDEs) that allows to work on the code of a recipe completely independent from bitbake. bitbake is only called if the configuration or the whole SDK has to be regenerated. But bitbake should not need to be called while working in the IDE. This has two major advantages over calling devtool build from the IDE: - The IDE provides plugins for integration with cmake, for example. These features are usable, which would not be the case if bitbake or devtool are called from within the IDE. - It is much faster. Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Configuration menu - View commit details
-
Copy full SHA for 4c5e2bf - Browse repository at this point
Copy the full SHA 4c5e2bfView commit details -
tests: add a C++ example recipe
This simple C++ project supports compilation with cmake and with meson. It's supposed to be used with oe-selftest for the devtool ide plugin. Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Configuration menu - View commit details
-
Copy full SHA for 05453ed - Browse repository at this point
Copy the full SHA 05453edView commit details -
cmake-example: workaround for pseudo breakeage
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Configuration menu - View commit details
-
Copy full SHA for b8a5ddd - Browse repository at this point
Copy the full SHA b8a5dddView commit details -
devtool: refactor deploy-target
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Configuration menu - View commit details
-
Copy full SHA for a80eabf - Browse repository at this point
Copy the full SHA a80eabfView commit details -
devtool: ide make deploy-target quicker
Instead of calling devtool deploy-target which starts a bitbake server to get some variables the previous refactoring allows to generate a simple script which does no longer depend on variables from bitbake. This is much faster.
Configuration menu - View commit details
-
Copy full SHA for 199bb41 - Browse repository at this point
Copy the full SHA 199bb41View commit details -
oe-selftest devtool: ide tests
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Configuration menu - View commit details
-
Copy full SHA for 44f8a81 - Browse repository at this point
Copy the full SHA 44f8a81View commit details -
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Configuration menu - View commit details
-
Copy full SHA for ca80f50 - Browse repository at this point
Copy the full SHA ca80f50View commit details
There are no files selected for viewing