Skip to content

Conversation

@irieger
Copy link
Contributor

@irieger irieger commented Nov 23, 2025

Summary

Changes to recipe: libx265/3.6 & libx265/4.1

Motivation

I realized that the current version of libx265 is somewhat dated already (and not even on the official release server). Also the gitlab mirror isn't kept up to date so it might be better to pull downloads from the original source.

In the meantime, quite some work was spent in both performance optimization (arm especially) as well as feature additions.

Details

Release notes are hidden a bit in the upstream repository: https://bitbucket.org/multicoreware/x265_git/src/master/doc/reST/releasenotes.rst


  • Read the contributing guidelines
  • Checked that this PR is not a duplicate: list of PRs by recipe
  • If this is a bug fix, please link related issue or provide bug details
  • Tested locally with at least one configuration using a recent version of Conan

Add a 👍 reaction to pull requests you find important to help the team prioritize, thanks!

ErniGH
ErniGH previously approved these changes Nov 24, 2025
Copy link
Contributor

@ErniGH ErniGH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Thanks for updating the patches

Comment on lines 18 to 20
+if(MSVC AND ARM64)
+ add_definitions("-DHAVE_NEON")
+endif()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Asking because I'm unsure, but do we still need these lines? I saw a lot of improvements regarding ARM64 NEON, but I still doubt it. What do you think? @irieger @ErniGH

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question. I had a look at the buildfile diffs but didn't study all the thousands of changes to the code itself. Can recheck in the next days.

Copy link
Contributor

@ErniGH ErniGH Nov 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. I’ve been looking into it, and it seems that between versions 3.4 and 3.6 the way NEON is detected has changed.
Screenshot 2025-11-28 at 12 20 58

I’m attaching the build logs for 3.6 and 4.1 without that part of the patch. Everything appears to work fine, so the new patches can omit that section.

3_6.log
4_1.log

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's remove that then 👍

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for finding and fixing, I'd only have had time to check on the weekend now but that saves me some time for other stuff ;)

Copy link
Contributor

@franramirez688 franramirez688 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks @irieger

@franramirez688 franramirez688 merged commit 3990da6 into conan-io:master Nov 28, 2025
10 checks passed
@irieger irieger deleted the libx265/3.6-and-4.1 branch November 28, 2025 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants