After Upgrade to 2023.9.339 version of NRF Connect Plugin for VScode, and a restart, projects have returned to the “The Build Configuration is stale. Run a Pristine Build” State.

RE: After Upgrade to 2023.9.339 version of NRF Connect Plugin for VScode, and a restart, projects have returned to the “The Build Configuration is stale. Run a Pristine Build” State.

Karl Ylvisaker — Tue, 03 Oct 2023 11:34:03 GMT

Hello,

Thank you for elaborating, and for updating on your current situation.
I am glad to read that it now seems to be resolved - I definitely think that this could trigger the 'stale build' issue you described earlier.

Please do not hesitate to ask if you should encounter any other issues or questions in the future! :)

Best regards,
Karl

RE: After Upgrade to 2023.9.339 version of NRF Connect Plugin for VScode, and a restart, projects have returned to the “The Build Configuration is stale. Run a Pristine Build” State.

Joe Kane — Mon, 02 Oct 2023 15:08:23 GMT

Hello Karl,

I did use the tool manager to uninstall and reinstall.

Actually, on my system there is a symbolic junction point that creates a virtual logical D drive. There is only one physical drive in the system (C:\), so symlink junction ' D:\' points to the sub-directory at 'C:\D'. Both should be equivalent but maybe this is confusing the latest plugin.

However, this same exact setup was working just fine on the prior versions of VScode plugin, unless maybe the uninstall/reinstall used different paths.

But this was a good clue.

the output of the query shows the NCS entries with d drive paths:

HKEY_CURRENT_USER\Software\Kitware\CMake\Packages\NcsToolchain
    308a637a0e3b346e3a3a66482bb8c2ed    REG_SZ    D:/Git/ncs/toolchains/v2.3.0/cmake
    d970e5fd2486c4e06195d6bbfee4f8a4    REG_SZ    D:/Git/ncs/toolchains/31f4403e35/cmake

So for experiment, I used regedit and changed the paths to be C drive based:

HKEY_CURRENT_USER\Software\Kitware\CMake\Packages\NcsToolchain
    308a637a0e3b346e3a3a66482bb8c2ed    REG_SZ    c:/d/Git/ncs/toolchains/v2.3.0/cmake
    d970e5fd2486c4e06195d6bbfee4f8a4    REG_SZ    c:/d/Git/ncs/toolchains/31f4403e35/cmake

I did lose the active board build configuration as a result, but after re adding it and rebuilding things seem to be working, and the stale build state is gone. I will work with it for a little to see if this holds.

RE: After Upgrade to 2023.9.339 version of NRF Connect Plugin for VScode, and a restart, projects have returned to the “The Build Configuration is stale. Run a Pristine Build” State.

Karl Ylvisaker — Mon, 02 Oct 2023 14:17:16 GMT

Hello,

Thank you for providing the additional information.

Our developers took a look at the generated support information and it looks to them like your toolchain installation has failed - it appears as though your toolchain is located in d:\Git, but the executables are found in c:\d\Git, which also seems to be the case for the SDK.
They speculate that you perhaps have some invalid paths somewhere in your setup.
Could you run the following command in a cmd terminal and share the output here?

reg query HKCU\Software\Kitware\CMake\Packages\NcsToolchain

In your previous ticket you said that you had tried to uninstall and reinstall the SDK and toolchain to see if this could fix the issue - could you confirm whether you did this through the manual installation of the SDK & Toolchain, or if you used the Toolchain Manager application in nRF Connect for Desktop?

[quote user="Joe Kane"]Can you share any detail about how nrf connect determines stale state that may shed a clue? Is it hashing particular files or paths or something?[/quote]

To determine if a build is stale it checks whether the build uses the compiler in the active toolchain, and that the SDK still matches.

Best regards,
Karl

RE: After Upgrade to 2023.9.339 version of NRF Connect Plugin for VScode, and a restart, projects have returned to the “The Build Configuration is stale. Run a Pristine Build” State.

Joe Kane — Fri, 29 Sep 2023 11:13:07 GMT

Karl,

Here is the file. Also a screen shot showing still in pristine state. While builds do work and debugging works, the device tree and other related build files (input files/output files) etc are unavailable from nrf connect in this state.

Can you share any detail about how nrf connect determines stale state that may shed a clue? Is it hashing particular files or paths or something?

Or maybe some detail about the first fix that was applied on my original ticket that could help?

devzone.nordicsemi.com/.../nrf_5F00_connect_5F00_support_5F00_info.zip

RE: After Upgrade to 2023.9.339 version of NRF Connect Plugin for VScode, and a restart, projects have returned to the “The Build Configuration is stale. Run a Pristine Build” State.

Karl Ylvisaker — Fri, 29 Sep 2023 10:01:55 GMT

Hello again,

Everything looks quite right here - there is nothing in the build the build that should make it appear stale.

Can you also generate support information and upload it here? Open command palette (ctrl+shift+p or View > Command Palette) and write nRF Connect: Generate support information. When you select this the information should be generated in the output terminal windows.
Then our VSC Extension developers can take a look and see if they can spot the cause of this issue.

Best regards,
Karl

RE: After Upgrade to 2023.9.339 version of NRF Connect Plugin for VScode, and a restart, projects have returned to the “The Build Configuration is stale. Run a Pristine Build” State.

Joe Kane — Thu, 28 Sep 2023 14:45:54 GMT

Karl,

Here is an entire zipped blinky project . I deleted the build folder, did a pristine build. all logs and files should be there for you.devzone.nordicsemi.com/.../sandbox.zip

RE: After Upgrade to 2023.9.339 version of NRF Connect Plugin for VScode, and a restart, projects have returned to the “The Build Configuration is stale. Run a Pristine Build” State.

Karl Ylvisaker — Thu, 28 Sep 2023 13:26:14 GMT

Hello again,

Could you fully delete the 'build' folder, do a pristine build, and provide the full log from your build when this happens?
If you could also share your CMakeCache.txt (at least for ZEPHYR_BASE, CMAKE_C_COMPILER, but the whole thing would be most helpful) that would also be very helpful! :)

Best regards,
Karl

RE: After Upgrade to 2023.9.339 version of NRF Connect Plugin for VScode, and a restart, projects have returned to the “The Build Configuration is stale. Run a Pristine Build” State.

Karl Ylvisaker — Thu, 28 Sep 2023 11:45:29 GMT

Hello,

Thank you for your patience with this.
I have reached out to the developers again and I will update you as soon as I hear back from them.

Best regards,
Karl