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.ndk] revert change to keep align with ndk 22/23 #1

Conversation

unicornx
Copy link

@unicornx unicornx commented Apr 3, 2023

We are using latest ndk header files from google upstream, which is different against the ndk matching chrome 109.
For ./toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/android/looper.h, new version marked ALooper_pollAll with "__REMOVED_IN(1)", while in ndk for chrome 109, there is no such flag.

Diff and see only this change happened for looper.h.

Current solution: revert and removed the "__REMOVED_IN(1)".

FIXME: The final solution may be a new ndk, with:

  • proper files match ndk 22/23 that chrome 109 depends on
  • proper kernel uapi header files of 5.10 that aosp12/riscv64 for T-HEAD dev board.

We are using latest ndk header files from google upstream, which is
different against the ndk matching chrome 109.
For ./toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/android/looper.h,
new version marked ALooper_pollAll with "__REMOVED_IN(1)",
while in ndk for chrome 109, there is no such flag.

Diff and see only this change happened for looper.h.

Current solution: revert and removed the "__REMOVED_IN(1)".

FIXME: The final solution may be a new ndk, with:
- proper files match ndk 22/23 that chrome 109 depends on
- proper kernel uapi header files of 5.10 that aosp12/riscv64
  for T-HEAD dev board.

Signed-off-by: Wang Chen <[email protected]>
@unicornx unicornx self-assigned this Apr 3, 2023
@unicornx unicornx merged commit 6f6284e into aosp-riscv:riscv64_109.0.5414.87_dev Apr 3, 2023
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