We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It will be easier to integrate.
The alternative would be to re-implement the whole project in rust, and rely on its paradigm (using crates.io?)
For the record UnifySDK/build/cargo is 9GB:
du -hsc ../UnifySDK/build/cargo/* 1.2G ../UnifySDK/build/cargo/uic_gms_build 1.2G ../UnifySDK/build/cargo/uic_image_provider_build 1.2G ../UnifySDK/build/cargo/uic_nal_build 1.4G ../UnifySDK/build/cargo/uic_upti_cap_build 1.1G ../UnifySDK/build/cargo/uic_upti_writer_build 1.1G ../UnifySDK/build/cargo/uic_upvl_build 2.2G ../UnifySDK/build/cargo/unify_build 9.0G total
I am not a rust expert but I don't think we want that
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It will be easier to integrate.
The alternative would be to re-implement the whole project in rust, and rely on its paradigm (using crates.io?)
For the record UnifySDK/build/cargo is 9GB:
I am not a rust expert but I don't think we want that
The text was updated successfully, but these errors were encountered: