-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Buildstream SDK] x265 encoder support #15864
Conversation
EWS run on current version of this PR (hash a42b305) |
+- if(ARM AND CROSS_COMPILE_ARM) | ||
+- if(ARM64) | ||
+- set(ARM_ARGS -fPIC) | ||
+- else() | ||
+- set(ARM_ARGS -march=armv6 -mfloat-abi=soft -mfpu=vfp -marm -fPIC) | ||
+- endif() | ||
+- message(STATUS "cross compile arm") | ||
+- elseif(ARM) | ||
+- if(ARM64) | ||
+- set(ARM_ARGS -fPIC) | ||
+- add_definitions(-DHAVE_NEON) | ||
+- else() | ||
+- find_package(Neon) | ||
+- if(CPU_HAS_NEON) | ||
+- set(ARM_ARGS -mcpu=native -mfloat-abi=hard -mfpu=neon -marm -fPIC) | ||
+- add_definitions(-DHAVE_NEON) | ||
+- else() | ||
+- set(ARM_ARGS -mcpu=native -mfloat-abi=hard -mfpu=vfp -marm) | ||
+- endif() | ||
+- endif() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This logic doesn't make much sense to me.
- Why making a difference between the flags passed to the compiler when cross-compiling and when not?. We do care about redistributable binaries on the SDK. So we should always build with compatible flags to the minimum baseline supported at run-time and not use as baseline whatever the CPU that builds the SDK happens to have. So I suggest to avoid using flags like
-mcpu=native
- Why use
march=armv6 -mfloat-abi=soft
for ARMv7 when cross-compiling but end using-mcpu=native -mfloat-abi=hard
when building natively for ARMv7?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I copied those patches from https://github.com/rpmfusion/x265/
I can remove the ones related with armv6/7 if needed, we don't support those legacy arches anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, is fine I guess. If in the end we end supporting armv7 this needs an update but right now we don't support it.
+- if(ARM AND CROSS_COMPILE_ARM) | ||
+- set(ARM_ARGS -march=armv6 -mfloat-abi=soft -mfpu=vfp -marm -fPIC) | ||
+- elseif(ARM) | ||
+- find_package(Neon) | ||
+- if(CPU_HAS_NEON) | ||
+- set(ARM_ARGS -mcpu=native -mfloat-abi=hard -mfpu=neon -marm -fPIC) | ||
+- add_definitions(-DHAVE_NEON) | ||
+- else() | ||
+- set(ARM_ARGS -mcpu=native -mfloat-abi=hard -mfpu=vfp -marm) | ||
+- endif() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here than commented above.
https://bugs.webkit.org/show_bug.cgi?id=259242 Reviewed by Carlos Alberto Lopez Perez. For WPT WebCodec tests we need an HEVC software encoder, since the bots don't have GPU capabilities for hardware encoding. * Tools/buildstream/elements/freedesktop-sdk.bst: * Tools/buildstream/elements/sdk-platform.bst: * Tools/buildstream/patches/fdo-0009-gst-plugins-bad-Enable-x265-encoder.patch: Added. Canonical link: https://commits.webkit.org/266098@main
a42b305
to
ca2221a
Compare
Committed 266098@main (ca2221a): https://commits.webkit.org/266098@main Reviewed commits have been landed. Closing PR #15864 and removing active labels. |
ca2221a
a42b305