-
Notifications
You must be signed in to change notification settings - Fork 3k
Add .inc as a header file type. #9715
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
Conversation
Currently, if you were to add a directory that only contained .inc files, this file would not be passed as an include path to the compiler. This ensures that .inc files are also considered header files.
It's a fix and it's fine, but do we want to support this as a valid header file type? |
Ah, that would be why. Poop. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I initially approved but rethink this
Do we want to support .inc
, is this valid extension and not just "one project has it, we add it" ? When should I choose .h/hh/hpp or inc ? I find .inc to have special meaning , some projects do it that way.
If this approved, do we have this documented ? extensions supported and why inc is in there (what should be in the file, is it regular header file, is it special like only templates, or even some code file) .
TF-M actually generated these files according to their secure partitions manifests.
Probably this will be the description for having .inc supported.
@0xc0170 than what do you suggest? patching an external imported code and replace all includes of From a short googling I can see that it is a valid extention for headers: |
I just want to have this documented if we support it - "what extensions we support" that is it. Not repatching external code as .inc is valid extension. |
Where should it be documented? |
Hi @0xc0170, I wasn't aware of that doc, I'll add it to the list |
Hi @0xc0170, I've read that I've also added a corresponding doc update, thanks again for the prod: ARMmbed/mbed-os-5-docs#952 |
CI started |
Test run: SUCCESSSummary: 12 of 12 test jobs passed |
Description
This was brought up by a thread on one of the TF-M prs. They are integrating an existing project into Mbed OS, and the existing project uses
.inc
files for some generated headers.Currently, if you were to add a directory that only contained
.inc
files, this file would not be passed as an include path to the compiler. This ensures that.inc
files are also considered header files.Their build just so happens to work because the
.inc
files are generated in a directory that also contains a.h
file. So the directory is marked as an include path.I think this qualifies as a "fix" but let me know if I should change it.
Pull request type
Reviewers
@theotherjimmy