-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Feature Request] Enable completely disabling the heap through CMake #594
Comments
Hi @CrustyAuklet, |
Could you try my fork / apply this commit and see if that fixes your issue? I haven't actually tested it yet as I do not currently have a build setup to use the FreeRTOS-Kernel using the Cmake lists, but it should work if you add |
That works too, and I think I like a little better. I wasn't sure if it was OK to add another variable but it is a bit more explicit that way. |
This feature is included in #807. User now don't have to define FREERTOS_HEAP in cmake if heap is not required. |
Is your feature request related to a problem? Please describe.
I am using FreeRTOS on a very small MCU where we want no heap implementation. This is normally done by
setting
configSUPPORT_DYNAMIC_ALLOCATION
to 0. But I don't see a way to disable the heap via CMake.Describe the solution you'd like
I would like to be able to set the CMake cache variable
FREERTOS_HEAP
to a "falsey" string and have no heap file added tothe project. Strings that CMake considers false are described here
I think this is a pretty simple fix, to change the generator expression to
I have this in a branch on my fork here
Describe alternatives you've considered
Looking at the CMakeLists.txt in this repo I don't see a lot of other options. I tried setting
FREERTOS_HEAP
to an empty string and it tried to addportable/MemMang/heap_.c
to the project. I tried just using a heap file but then I get the errorHow many devices will this feature impact?
thousands
What are your project timelines?
Working on an MVP shipping date in January
Additional context
None.
If you have the same (or similar) feature request, please upvote this issue with thumbs up 👍
and use the comments section to provide answers to the questions above.
The text was updated successfully, but these errors were encountered: