-
-
Notifications
You must be signed in to change notification settings - Fork 398
Local .h files should not be treated as libraries #821
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
Comments
Duplicate of #484 |
A minimal demonstration of the issue: Set things up:
Now let's test with a build path not in the sketch folder just to make sure everthing is fine:
Looks good. Note that
Now to attempt using the sketch folder as the build folder:
Note that this time
I notice it works differently on Windows
Looks good, but if you want to do it again, you must remember to remove build.option.json first:
If you don't, everything in the sketch folder is deleted:
Hi @ArminJo. Just so I can try to fully understand the use case, is there a specific reason for wanting the build output to be saved to the root of the sketch folder? #687 means that when using Arduino CLI 0.11.0 and newer, all build artifacts (e.g., .hex, .elf, .bin) are saved to the
Do you foresee that build files other than the artifacts will be useful in the context of CI/CD? |
I somewhat recall that the Arduino IDE actually actively forbids making the build path equal to the sketch path (which makes sense, since the build path should really contain only temp files that can be entirely deleted if needed). So indeed, I wonder if this is something that should be fixed, or maybe must forbidden. |
@per1234 Thank you so much for investigating further. 🥇 |
Bug Report
Current behavior
Compiles with 0.10.0 and relative path
Fails with 0.10.0 and absolute path and additional --build-path parameter with
fatal error: img0_128x64c1.h: No such file or directory, but file is in the same directory as the .ino file.
Expected behavior
Local .h files should not be treated as libraries and if so, should not lead to an error!
Environment
The text was updated successfully, but these errors were encountered: