-
Notifications
You must be signed in to change notification settings - Fork 186
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
Making container node sizes
optional?
#143
Comments
Seconding this - I'm having the exact same issue. I don't know what might cause the size of nodes to change between builds, but it seems to me like |
The header is no longer re-generated if it already exists. If someone wants to do more sophisticated guarding against CMake changes (I don't know whether it's necessary), feel free to do a PR. If you want to disable the header entirely, it is enough to use CMake to create an empty file at that location. |
That's great, thank you! |
Hello, I have questions about the
container node sizes
stuff, motivated by (a) not really grasping what exactly it's for and (b) the amount of time it's adding to my configure step every time I re-run CMake.FOONATHAN_MEMORY_BUILD_TOOLS
, but now it runsget_container_node_sizes
unconditionally on every CMake invocation. Is this correct? And is it necessary?Perhaps relevant:
memory
library using CMakeFetchContent
and then doingadd_subdirectory
withEXCLUDE_FROM_ALL
. Perhaps this is too off-label. It just happens to be the way I get the other dependencies for my project.memory
, like making my own pools. I'm just using it to get polymorphic-memory-resource like behaviour so I can switch between a small number of pre-existing allocators.The text was updated successfully, but these errors were encountered: