-
Notifications
You must be signed in to change notification settings - Fork 8
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
Use "mpp" from apt instead of building from source #16
Conversation
Hmm, apparently this only works on Radxa images. Or maybe they have a separate repo, let me check |
eb0c62f
to
245223d
Compare
turned out to be more difficult than I expected. Will make another attempt later |
Does the Radxa repo include gst plugins for |
You can see what is in their repo here https://radxa-repo.github.io/bullseye/files.list But the problem with this PR is that Radxa repo is obviusly not included in standard Debian image and for some reason my attempts to add it fail. |
Peeking into here https://radxa-repo.github.io/bullseye/pkgs.json I don't see librockchip-mpp-dev at all. |
It's present and available in rsdk builds. |
245223d
to
2f06ea2
Compare
Finally success. The trick was to add 2 repositories, not one:
Now build takes ~4 minutes instead of ~8! |
This is for Radxa only, for the orange pi series one must add a separate repo. I've been using this: |
@JohnDGodwin A-ha.. interesting. Well, we are using this library here just to test that pixelpilot can be successfully compiled on Debian Bullseye arm64 in GitHub CI. We can't run pixelpilot for real in CI because we don't have actual rockchip available in CI. Do you think building pixelpilot with Raspberry version of the library will make any difference? |
Or you saying we need to mention this PPA in the README? |
No description provided.