You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Small changes in a source file should trigger an incremental build. Instead make performs a full build. See also this old CDT forum entry: https://www.eclipse.org/forums/index.php/t/1108303/
To Reproduce
Steps to reproduce the behavior:
Create a managed build project with an external make builder.
Show a projects resource in the Device Shell. E.g. right click on a projects folder Show In -> Device Shell
Try to rename the project. The rename should fail due to missing (write) access on the projects folder.
Make a small change in a source file.
Build the project.
A full build will be performed instead of only compiling the changed resource.
Expected behavior
The rename should not be performed when not all resources in a project can be accessed for writing.
Screenshots
A failed rename can lead to a not renamed refresh policy setting:
Not sure, maybe the fix has to be done not in CDT. This has to be invetigated.
ghentschke
changed the title
Incremental build is not working properly with external builder
Incremental build is not working correctly with external builder
Nov 21, 2024
Maybe we can add a check prior to the incremental build that the resource in the refresh policy does not match the current project and give a warning to the user.
Describe the bug
Small changes in a source file should trigger an incremental build. Instead
make
performs a full build. See also this old CDT forum entry: https://www.eclipse.org/forums/index.php/t/1108303/To Reproduce
Steps to reproduce the behavior:
Create a managed build project with an external make builder.
Show a projects resource in the Device Shell. E.g. right click on a projects folder
Show In
->Device Shell
Try to rename the project. The rename should fail due to missing (write) access on the projects folder.
Make a small change in a source file.
Build the project.
A full build will be performed instead of only compiling the changed resource.
Expected behavior
The rename should not be performed when not all resources in a project can be accessed for writing.
Screenshots
A failed rename can lead to a not renamed refresh policy setting:
This can cause random behavior of the incremental build. See also this failure/solution description from 2015: https://mcuoneclipse.com/2015/06/06/eclipse-project-refresh-policy-broken-incremental-build-with-external-make/
Version Information (please complete the following information):
The text was updated successfully, but these errors were encountered: