-
Couldn't load subscription status.
- Fork 932
add: cmakelist #1131
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
base: master
Are you sure you want to change the base?
add: cmakelist #1131
Conversation
Tests passed ✓, Code: 17112 B (+0.0%), Stack: 1448 B (+0.0%), Structs: 812 B (+0.0%)
|
|
Не могли бы вы написать комментарии в коде на английском? Так они будут полезны гораздо более широкой аудитории. |
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.
| # todo: add module CMSIS | ||
|
|
||
| # Перечисление зависимостей | ||
| # list(APPEND ${PROJECT_NAME}_DEPENDENCIES | ||
| # CMSIS | ||
| # typedef | ||
| # ) |
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.
Why are these here? Seems undesirable.
|
I think the best path for cmake support at the moment would be if someone volunteered to host/maintain a CMakeLists.txt outside of this org. We could add a link to it in the README.md (and eventually website) to direct potential users, like we have with littlefs-python, littlefs2-rust, etc. If such a CMakeLists.txt matures, and there's interest, I can eventually bring it into this org as an "official(?)" repo and volunteer to maintain it. But 1. I don't think it's high-priority, and 2. I'm not yet convinced there's a single CMakeLists.txt that covers enough use cases to be worth the maintenance headache. |
No description provided.