Closed alirana01 closed 1 month ago
The changes introduce pre-build checks in the IDFBuildConfiguration
class to ensure the project and environment IDF paths match. This involves adding the ProjectDescriptionReader
and IDFEnvironmentVariables
for handling project descriptions and environment variables. Additionally, new messages related to these checks are included in the Messages
class and messages.properties
file.
File Path | Change Summary |
---|---|
.../idf/core/build/IDFBuildConfiguration.java |
Added imports for ProjectDescriptionReader and IDFEnvironmentVariables , and introduced buildPrechecks method. |
.../idf/core/build/Messages.java |
Added a new string constant IDFBuildConfiguration_PreCheck_DifferentIdfPath . |
.../idf/core/build/messages.properties |
Updated to include messages related to project refreshing and ESP-IDF path configuration. |
.../idf/core/util/ProjectDescriptionReader.java |
Added getIdfPath method and modified getAppElfFileName method. |
.../idf/ui/tools/ToolsJob.java |
Removed a line that prints line to the console within a while loop. |
In the realm of code we tread,
Paths must match, the message said.
Pre-build checks, a safeguard true,
Ensuring paths align for you.
With tools refined, our task is clear,
A smoother build, no need to fear.
In lines of code, our journey's bright,
A coder's dream, in bytes of light.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
@alirana01 hi !
Tested under: OS - Windows 10 ESP-IDF: v5.2.1 / v5.1.1
let's add "\n" after every string to make it easier to read:
from:
to:
@alirana01
Tested under: OS - Windows 10
Multiple projects scenario:
@AndriiFilippov please verify after the recent builds the suggested changes
@alirana01
Tested under: OS - Windows 10
Multiple projects scenario:
- install v5.2 -> create and build project A
- install and activate v5.11 -> create and build project B
- select project A in Project Explorer and then select project B again. Try to build. Getting this message:
@alirana01 hi !
Issue is still persist.
@alirana01 Tested under: OS - Windows 10 Multiple projects scenario:
- install v5.2 -> create and build project A
- install and activate v5.11 -> create and build project B
- select project A in Project Explorer and then select project B again. Try to build. Getting this message:
@alirana01 hi !
Issue is still persist.
Please see again sorry for missing the original point in the comment should be fixed now
@alirana01 hi !
LGTM now 👍 Also tested with Custom Build folder. Works ✔️
No installed tools targets duplicate ✔️
Description
ESP-IDF Version Switching and build impact. The build was not working and not showing any proper message to user if the active version was switched and project was built using someother version of idf. Now added a proper message to the console to let user know they need to clean before trying to build the project with currently active version Also fixed redundant output of the targets when activating a different idf version from esp-idf manager
Fixes # (IEP-1230, IEP-1231)
Type of change
Please delete options that are not relevant.
How has this been tested?
Please follow steps in original ticket to verify
Test Configuration:
Checklist
Summary by CodeRabbit
New Features
Bug Fixes
Improvements
Refactor