Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Q: How to implement closed-source SoCs(separation of concerns) with different teams. #2

Open
crlf0710 opened this issue Mar 31, 2024 · 0 comments
Open

Q: How to implement closed-source SoCs(separation of concerns) with different teams. #2

crlf0710 opened this issue Mar 31, 2024 · 0 comments

Comments

@crlf0710
Copy link

Reusing rlibs between teams is possible today

ABI unstability is not an issue if rustc version is pinned.

Skip using cargo if closed-source is what you need

rustdoc can provide equivalent to C/C++ header information to downstream rust crates

cbindgen and other tools can prepare C/C++ headers for ffi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@crlf0710