diff options
| -rwxr-xr-x | scripts/lib/devtool/ide_sdk.py | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/scripts/lib/devtool/ide_sdk.py b/scripts/lib/devtool/ide_sdk.py index 42ac20c654..f8cf65f4a8 100755 --- a/scripts/lib/devtool/ide_sdk.py +++ b/scripts/lib/devtool/ide_sdk.py | |||
| @@ -927,6 +927,15 @@ def ide_setup(args, config, basepath, workspace): | |||
| 927 | def register_commands(subparsers, context): | 927 | def register_commands(subparsers, context): |
| 928 | """Register devtool subcommands from this plugin""" | 928 | """Register devtool subcommands from this plugin""" |
| 929 | 929 | ||
| 930 | # The ide-sdk command bootstraps the SDK from the bitbake environment before the IDE | ||
| 931 | # configuration is generated. In the case of the eSDK, the bootstrapping is performed | ||
| 932 | # during the installation of the eSDK installer. Running the ide-sdk plugin from an | ||
| 933 | # eSDK installer-based setup would require skipping the bootstrapping and probably | ||
| 934 | # taking some other differences into account when generating the IDE configurations. | ||
| 935 | # This would be possible. But it is not implemented. | ||
| 936 | if context.fixed_setup: | ||
| 937 | return | ||
| 938 | |||
| 930 | global ide_plugins | 939 | global ide_plugins |
| 931 | 940 | ||
| 932 | # Search for IDE plugins in all sub-folders named ide_plugins where devtool seraches for plugins. | 941 | # Search for IDE plugins in all sub-folders named ide_plugins where devtool seraches for plugins. |
