Skip to content

Sloeber does not tag the compiler error "g++: error: ..file_opts: No such file or directory" as an error #1697

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jantje opened this issue Dec 1, 2024 · 2 comments
Assignees
Labels
status: no good solution found (yet) We don't know how to fix this.

Comments

@jantje
Copy link
Member

jantje commented Dec 1, 2024

As reported in #1694

@jantje jantje self-assigned this Dec 1, 2024
@jantje
Copy link
Member Author

jantje commented Dec 14, 2024

Investigating this issue I found that the error count is not always zero.
The reported case is actually caused by ESP32 2.0.14 and the file_opts error.
The compiler givers the error but the error does not get recognized by the error parser.
xtensa-esp32s3-elf-g++: error: R:\runtime-sloeber.product\test\bin\Release/file_opts: No such file or directory
On top of that the internal builder does not skip the post build action resulting in hiding the error.

As I don't know how to fix the error parser (standard CDT component) and that is also a issue in Sloeber V4 I decided to dedicate this issue (probably won't fix) to the not reported error and create a new issue V5 isssue for the post build commands not being skipped in case of an error.

@jantje jantje changed the title V5.0 failed build ends with 0 erros 0 warnings. Sloeber does not tag the compiler error "g++: error: ..file_opts: No such file or directory" as an error Dec 14, 2024
@jantje
Copy link
Member Author

jantje commented Dec 14, 2024

Seems you can add regular expressions to the error parsers but I failed to get the error to be recognized.

@jantje jantje added the status: no good solution found (yet) We don't know how to fix this. label Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: no good solution found (yet) We don't know how to fix this.
Projects
None yet
Development

No branches or pull requests

1 participant