Skip to content

Conversation

@lcy0321
Copy link

@lcy0321 lcy0321 commented Nov 9, 2025

Refer to the build workflow of llama.cpp to add a Windows ROCm (HIP) build release to the workflow.
Since there are many differences between the HIP build and other builds, this PR add a separate "windows-latest-cmake-hip" job, instead of enabling the ROCm matrix entry in the existing Windows build job.

Main differences include:

  • Install ROCm SDK from AMD official installer.
  • Add a cache step for ROCm installation and a ccache step for build processing, since the HIP build takes much longer time than other builds.
  • Include the ROCm/HIP artifact in the release assets.

Also fix some minor build issues:

  • correct Vulkan SDK installation condition in build workflow
  • fix missing commit sha in macOS and Ubuntu build zip name

The release is successfully created in my forked repository:
https://github.com/lcy0321/stable-diffusion.cpp/releases/tag/master-353-1d8e65a

The build workflows for macOS and Ubuntu incorrectly check for the
"main" branch instead of "master" when retrieving the commit hash for
naming the build artifacts.
Refer to the build workflow of llama.cpp to add a Windows ROCm (HIP)
build release to the workflow.
Since there are many differences between the HIP build and other
builds, this commit add a separate "windows-latest-cmake-hip" job,
instead of enabling the ROCm matrix entry in the existing Windows
build job.

Main differences include:

- Install ROCm SDK from AMD official installer.
- Add a cache step for ROCm installation and a ccache step for build
  processing, since the HIP build takes much longer time than other
  builds.
- Include the ROCm/HIP artifact in the release assets.
@lcy0321 lcy0321 marked this pull request as ready for review November 9, 2025 13:15
@lcy0321
Copy link
Author

lcy0321 commented Nov 10, 2025

Hi @leejet,
Could you take a look at this PR?
I’m not sure which maintainers I should notify.

@stduhpf
Copy link
Contributor

stduhpf commented Nov 10, 2025

I’m not sure which maintainers I should notify.

Only leejet can merge PRs, just give him some time.

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