-
Notifications
You must be signed in to change notification settings - Fork 217
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
Private headers should not be needed to build CCF apps #2428
Comments
|
Listing some thoughts on the refactoring needed for remaining components, so I don't lose track of them:
|
Our sample apps also directly includes some private headers, rather than going via public includes:
I think these are all simple to fix, though the |
We've finished the major work here, and the only major type that we still need to expose is Beyond that, the remaining cleanup tasks are:
|
Longer term follow-up to #697. We currently implement much of the project in headers, and so our public headers include private headers which must be installed to build CCF apps. We should break these dependency chains to make a hard distinction between publicly supported APIs and implementation details. This will likely involve moving more implementations to
.cpp
files, and separating the project into individually built libraries.The text was updated successfully, but these errors were encountered: