Forward ABI compatibility of Frame #479
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Frame allocates memory with new[] by default. Provide a way to not do that.
Merged
Contributor
|
Just tested this on my MacBook Air and it compiles and runs well 👍 |
floe
added a commit
that referenced
this pull request
Nov 27, 2015
Forward ABI compatibility of Frame
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Frameright now always allocates memory and there is no way to turn it off.In the future, VT, VAAPI, and Tegra JPEG decoder, and CUDA processor all need to use custom memory allocators, and they will have to break ABI without this.
Example of how VT decoder changes it: https://github.com/OpenKinect/libfreenect2/pull/365/files#diff-7bd5995c21c16482ff1a19a27816180dL58