-
Notifications
You must be signed in to change notification settings - Fork 3k
Recognize ".cc" and ".hh" source file extensions #7437
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
".cc" --> C++ source code ".hh" --> header This change allows existing source code with this naming convention (e.g. my company's) to be used in mbed.os projects.
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.
LGTM
@theotherjimmy Any objections? |
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'll have to rebase my refactor-resources pr when this goes in, or you'll have to rebase this.
/morph build |
Build : SUCCESSBuild number : 2553 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 2198 |
Test : SUCCESSBuild number : 2310 |
/morph mbed2-build |
@snej Thanks for the contribution |
Recognize ".cc" and ".hh" source file extensions
Description
Minor change to the Python
mbedToolchain
class to recognize the commonly used filename extensions ".cc" (C++ source code) and ".hh" (C++ header). Without this change, source code with this naming convention (e.g. my company's entire sourcebase) is ignored by the CLI.Tested by building a project containing source code with such filename suffixes.
Pull request type