Skip to content
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

fdk-aac encoder + libshout-idjc + vcpkg Windows dependencies integration #3615

Merged
merged 58 commits into from
Feb 22, 2021

Conversation

Be-ing
Copy link
Contributor

@Be-ing Be-ing commented Feb 4, 2021

This is a rebased combination of #3543 and #3594 which enables AAC encoding on Windows, macOS, and Linux.

Stéphane L and others added 30 commits January 8, 2021 23:51
@Be-ing
Copy link
Contributor Author

Be-ing commented Feb 17, 2021

Now with TagLib 1.12 on Windows and macOS

Copy link
Contributor

@uklotzde uklotzde left a comment

Choose a reason for hiding this comment

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

Just one minor remark where I think an additional comment would help.

The complexity and sheer amount of code is not caused by this PR that just tries to tie everything together. Even if it might (or almost certainly will) cause unforeseeable issues that we missed during the review, I expect those will be fixable. We urgently need some real world tests of this code.

First I was skeptical about switching to the idjc for. But now I consider it the lesser evil compared to the original libshout.

I trust you on the statement that the dynamic loading works on all platforms.

CMakeLists.txt Show resolved Hide resolved
CMakeLists.txt Show resolved Hide resolved
elseif(FDK_AAC_LIBRARY)
message(STATUS "Found fdk-aac: ${FDK_AAC_LIBRARY}")
else()
message(STATUS "Could NOT find fdk-aac")
Copy link
Contributor

Choose a reason for hiding this comment

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

I am also against repeating the inner workings of the find algorithm in colloquial language, maybe even with platform-dependent wording. This message will only ever be seen by developers and is sufficient.

@Be-ing
Copy link
Contributor Author

Be-ing commented Feb 18, 2021

Merge?

Copy link
Contributor

@uklotzde uklotzde left a comment

Choose a reason for hiding this comment

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

@Holzhaus @daschuer Do you agree?

I would like to merge this as a baseline and resolve any open issues that might occur later. I expect that reviewing individual improvements would be easier and hopefully less controversial afterwards.

@Be-ing
Copy link
Contributor Author

Be-ing commented Feb 18, 2021

The longer this sits open, the more will pile on top.

@Be-ing
Copy link
Contributor Author

Be-ing commented Feb 21, 2021

ping

@Be-ing
Copy link
Contributor Author

Be-ing commented Feb 22, 2021

Is someone going to press merge or are we going to delay this release indefinitely?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants