[wip] llgo:pretest embed customize clang

[luoliwoshang]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

feature

• building esp-clang from source
• add test embed target

verify in follow platform

• macos arm64
• macos amd64
• linux arm64
• linux amd64

[luoliwoshang]

Hi @carlocab ,
I hope you're doing well! I'm working on a formula for llgo that has a dependency on a custom-built espressif/llvm-project (Fork of LLVM with Xtensa specific patches).
The build process is currently exceeding the default time limits in the CI system, which is causing build failures. Given that this involves building LLVM from source with custom patches, it's inherently a time-intensive process.
Would it be possible to add the long_build label to this formula? This would help accommodate the extended build time required for the LLVM compilation.
I really appreciate your time and assistance with this. Thank you for all the great work you do maintaining Homebrew!
Best regards

[luoliwoshang]

Hi @chenrui333 , hope you're having a great day!
I'm submitting a formula for llgo that depends on a custom espressif/llvm-project build (LLVM fork with Xtensa-specific patches). The formula is running into CI timeout issues since building LLVM from source with these patches takes quite a while.
I was wondering if we could add the long_build label to help with the extended compilation time? The LLVM build process is naturally time-consuming, especially with the custom patches included.
Thanks so much for taking a look, and really appreciate all the amazing work you do for the Homebrew community!
Cheers!

[carlocab]

What are your plans for upstreaming your changes from this fork?

We're not that keen on another custom build of LLVM here.

[luoliwoshang]

@carlocab Thank you for your feedback!
I appreciate you bringing this up! We don't actually maintain or fork Espressif's LLVM repository—our executable simply uses it as a compiler to support building code for Xtensa architecture chips (such as ESP32) in llgo.
From what I understand, Espressif is actively working on upstreaming their Xtensa modifications to LLVM mainline. You can track their progress here: Tracking Issue for merging to upstream (LLVM-57) · Issue #4 · espressif/llvm-project.
We're also hoping this formula can eventually be merged into Homebrew/core, which would allow users to access it directly through the standard brew install llgo command without needing additional taps or custom configurations. This would greatly improve llgo's accessibility and community adoption.

[carlocab]

I'm not convinced that this formula is sufficiently popular to warrant the maintenance burden of yet another custom LLVM build here, I'm afraid. (See analytics data here.)

It looks to me that @espressif releases binary builds of their toolchain (example), so what we should probably do is stick with the LLVM formula here, but make it easier for users to use a custom toolchain with this formula.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[fxcoudert]

Agreeing with @carlocab above, and closing for now. This feels beyond the scope of what Homebrew ships. Probably good match for a personal tap: https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap