Skip to content

branch-4.1: [chore](build) Add simdutf third-party dependency #68369 - #68391

Open
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-68369-branch-4.1
Open

github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-68369-branch-4.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #68369

Problem Summary:

Add simdutf 9.2.0 as a backend third-party dependency. Register its
source archive and checksum, build and install the static library and
public headers, add the imported library to the backend dependency list,
and record its Apache-2.0 license. Existing UTF-8 validation
implementations and callers are unchanged.

Existing prebuilt third-party installations need the new library before
building BE. Refresh the third-party package or run
`./thirdparty/build-thirdparty.sh -j 48 simdutf` in the source checkout.
The regular third-party build includes it in the default package list.

### Release note

None

### Check List (For Author)

- Test
    - [ ] Regression test
    - [ ] Unit Test
    - [x] Manual test (add detailed scripts or steps below)
        - `bash -n thirdparty/vars.sh thirdparty/build-thirdparty.sh`
- `./thirdparty/build-thirdparty.sh -j 48 simdutf` completed on Linux
x86_64 with Clang 20.1.8, including download verification,
static-library/header installation, and source cleanup.
- Configured and built a standalone CMake smoke test using
`be/cmake/thirdparty.cmake`; verified the imported archive path and
membership in `COMMON_THIRDPARTY`, then linked and ran UTF-8 validation
and UTF-8-to-UTF-16 conversion checks against the installed library.
- `bash build-support/check-build-hygiene.sh` and `git diff --check`
passed.
        - Full BE compilation and ARM execution were not run.
    - [ ] No need to test or manual test. Explain why:

- Behavior changed:
    - [x] No.
    - [ ] Yes.

- Does this need documentation?
    - [x] No.
    - [ ] Yes.

### Check List (For Reviewer who merge this PR)

- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label
@github-actions
github-actions Bot requested a review from yiguolei as a code owner September 22, 2026 12:02
@hello-stephen

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@hello-stephen

Copy link
Copy Markdown
Contributor

run buildall

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.

2 participants