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

[chrome.ffmpeg] don't set toolchain_level forcely #4

Merged

Conversation

unicornx
Copy link
Contributor

@unicornx unicornx commented May 8, 2023

The original reason that AndroidApiLevels could not get correct level is due to android-ndk-ci didn't contain sysroot files for api-level 24. After hacking the android-ndk-ci and adding api-level 24 lib files, the build_ffmpeg.py can work.
Updated some auto-generated files together with this change.

Note, we now have to use https://github.com/aosp-riscv/android-ndk-ci, but not https://github.com/aosp-riscv/toolchain-prebuilts-ndk-r23 when running running build_ffmpeg.py. Because this script will use clang tools contained in the android ndk to build some files, but the android ndk from T-head can not work well, so I have to use android-ndk-ci(which actually use the clang we build ourselves) instead and it works for us.
I don't want to hack the android ndk from T-head because there are too many mess for ndk. Hopeing android ndk to be ready soon so we will not have so many troubles when porting chromium. I will update the document to point this out.

The original reason that AndroidApiLevels could not get correct level
is due to android-ndk-ci didn't contain sysroot files for api-level 24.
After hacking the android-ndk-ci and adding api-level 24 lib files,
the build_ffmpeg.py can work.
Updated some auto-generated files together with this change.

Note, we now have to use https://github.com/aosp-riscv/android-ndk-ci,
but not https://github.com/aosp-riscv/toolchain-prebuilts-ndk-r23 when
running running build_ffmpeg.py. Because this script will use clang
tools contained in the android ndk to build some files, but the
android ndk from T-head can not work well, so I have to use
android-ndk-ci(which actually use the clang we build ourselves)
instead and it works for us.
I don't want to hack the android ndk from T-head because there are
too many mess for ndk. Hopeing android ndk to be ready soon so we
will not have so many troubles when porting chromium.
I will update the document to point this out.

Signed-off-by: Wang Chen <wangchen20@iscas.ac.cn>
@unicornx unicornx self-assigned this May 8, 2023
@unicornx unicornx merged commit 15e5ff9 into aosp-riscv:riscv64_109.0.5414.87_dev May 8, 2023
@unicornx
Copy link
Contributor Author

unicornx commented May 8, 2023

Changes for android-ndk-ci is merged with aosp-riscv/android-ndk-ci#3.
Changes for doc is merged with aosp-riscv/working-group#58

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.

1 participant