Continually generating autotools configure script

[stevebroshar]

Uninstalled the extension since it was continually generating the configure script. I could detect that files (configure and config.log) were changing without my interaction and continually. An "ls -al config.log" reported a different size file each time. The size would increase for a while and then reset to smaller size. After uninstalling this extension, the issue stopped.

I assume the autotools config generator was running over and over. One never wants the config generator to run automatically.

And why the heck does this yocto extension do autotools stuff?

[deribaucourt]

Hello and thanks for your feedback.

Indeed the Yocto extension should never run autotools command (and it doesn't to my knowledge). I'd like to try to reproduce your issue. I attempted to configure and open gawk. Once I ran ./configure, the config.log did not change. What you observed may be due to more specific conditions, or a combination with other extensions. Could you please provide the following:

1. List of installed extensions code --list-extensions
2. Extension logs: Enable debug verbosity (Settings -> bitbake.loggingLevel), and dump the content of Output -> BitBake
3. List processes: ps | grep config

In the meantime, if you want to keep the extension for Yocto workspaces, you can simply "disable" it in the autotools workspaces rather than fully uninstalling.

[stevebroshar]

Note that the issue happened in the WSL environment. Maybe that's relevant.

To fix the issue yesterday, I uninstalled one extension at a time, restarting vscode after each uninstall. The issue stopped happening when I uninstalled vscode-bitbake extension. The list below shows the extensions still installed (that I didn't uninstall).

When I run that command in the Ubuntu terminal:
$ code --list-extensions
mads-hartmann.bash-ide-vscode
mcu-debug.debug-tracker-vscode
mindaro-dev.file-downloader
ms-python.debugpy
ms-python.python
ms-python.vscode-pylance
ms-vsliveshare.vsliveshare

Did find logging level setting and changed to verbose, but didn't find Output->Bitbake

ps | grep config: returns nothing

To verify the issue, I re-installed the vscode-bitbake extension today, but I cannot get autotools to run continually like yesterday.

[deribaucourt]

Thanks for going through the instructions.
Let me know if you can reproduce it. You'll find the logs near the terminals.
You can run the VSCode command "Output: Focus on Output View" to get there directly.
Then there's a sliding menu in the top right of that view where you can select BitBake