forked from yoctoproject/vscode-bitbake
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chore: Change the settings so the project scanner may work on different setups #13
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -62,45 +62,35 @@ | |
"debug" | ||
], | ||
"default": "error", | ||
"description": "Adjust the logging level. error: only errors; info: only information that is useful for the user; debug: the same like info, but with additional debug informations" | ||
"description": "Adjust the logging level: 'error' for reporting only errors, 'info' for displaying information useful to the user, and 'debug' for the same information as 'info,' but with additional debugging details." | ||
}, | ||
"bitbake.deepExamine": { | ||
"bitbake.shouldDeepExamine": { | ||
"type": "boolean", | ||
"default": false, | ||
"description": "Activates an deeply examine. If a recipe export an extra package that have not the same name like the recipe file the normal scan will not find this packages. If you like to find the packages you have to activate this option." | ||
"description": "Activate deep examination. If a recipe exports an additional package with a different name than the recipe file, the normal scan will not detect these packages. To find these packages, you need to activate this option." | ||
}, | ||
"bitbake.workingFolder": { | ||
"bitbake.pathToEnvScript": { | ||
"type": "string", | ||
"default": "vscode-bitbake-build", | ||
"description": "Use this setting to specify the build folder. Use other folder than for your regular 'build' to avoid collisions." | ||
"default": "oe-init-build-env", | ||
"description": "Set the path to the environment script to configure the BitBake project. If the file does not exist, the extension will attempt to configure the environment variables by itself." | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think we should attempt to configure the variables ourselves. Let's always ask for an env script as is the recommended Yocto workflow. |
||
}, | ||
"bitbake.generateWorkingFolder": { | ||
"type": "boolean", | ||
"default": true, | ||
"description": "Use this setting to specify whether or not to generate a build folder. Can help prevent git repo headaches." | ||
}, | ||
"bitbake.pathToBashScriptInterpreter": { | ||
"type": "string", | ||
"default": "/bin/bash", | ||
"description": "This interpreter is used to run bash scripts" | ||
}, | ||
"bitbake.machine": { | ||
"bitbake.pathToBuildFolder": { | ||
"type": "string", | ||
"default": "", | ||
"description": "This setting is used to forward the machine name to bitbake." | ||
"default": "build", | ||
"description": "Set the build folder for the BitBake project." | ||
}, | ||
"bitbake.pathToBitbakeFolder": { | ||
"type": "string", | ||
"default": "./bitbake", | ||
"description": "This setting is used to specify the path to the bitbake folder." | ||
"default": "sources/poky/bitbake", | ||
"description": "Set the path to the BitBake folder." | ||
} | ||
} | ||
}, | ||
"commands": [ | ||
{ | ||
"command": "bitbake.rescan-project", | ||
"title": "BitBake: Rescan Project", | ||
"description": "This command rescans the bitbake project." | ||
"description": "This command rescans the BitBake project." | ||
} | ||
] | ||
}, | ||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can be more specific than "work properly". The extension highlighting works without for instance. Maybe just "For all the features to be enabled,"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd also rephrase "it will make the following assumptions" -> "It will look for it at these default locations"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets remove it it in PR #16