Closed SpieringsAE closed 3 months ago
Hello, thanks for your report.
Before running any command, the shell environment has to browse to the path bitbake.workingDirectory
. Make sure to check this setting is properly configured in your workspace.
If you enabled the debug log level, you should see more input in the "Output" -> "Bitbake" and "Output" -> "Bitbake Language Server" views (as illustrated). Could you provide the logs produced in both of these pannels in your case?
Well, turns out I am a bit of an idiot, it seems I messed up bitbake.workingDirectory
parameter.
I didn't realize I could switch to different contexts in the 'output' view, so thats a nice thing to learn. But yeah with that setting fixed it seems to work now, I would not have thought of it without your hint though.
Many thanks for that!
Thanks for your feedback! Maybe this is something we could improve on, like adding a more detailed explanation when this kind of error is thrown. Either in our troubleshooting guide, or directly in the error popup.
When scanning it errors out at the start, yet when I open a terminal myself and enter the command it shows me, everything works:
Is what it shows me it executes. The chdir has to be the one at the end of oe-init-build-env, but when I try to debug print the $BUILDDIR variable I cannot see any output from the extension so I can't verify that it is correct there.
Is there a way I can get more debug info? I've tried changing the log level but I guess thats for a different purpose.