Package request: tilelang & tile-kernels

[h-vetinari]

Package name

tile-kernels & tilelang

Package version

Newest

Package website

https://github.com/deepseek-ai/TileKernels which depends on https://github.com/tile-ai/tilelang (https://tilelang.com)

Package availability

1. PyPI: tilelang, tile-kernels
2. Github: tilelang, tile-kernels

Additional comments

We'll need to revive https://github.com/conda-forge/libtvm-feedstock (and perhaps https://github.com/conda-forge/tvm-py-feedstock) for tilelang.

Package is not available

• The package is not available on conda-forge.

No previous issues or open PRs

• No previous issue exists and no PR has been opened.

[1minds3t]

Hi @h-vetinari — I saw this request and decided to help get this stack onto conda-forge.

I've opened PR #33145 (#33145) which adds the base recipe for tilelang.

While investigating the previously mentioned libtvm dependency, I checked the build outputs and dependency resolution paths. In the current configuration, I did not observe any linkage or runtime dependency on an external libtvm (no cmake discovery, no shared library linkage, and no runtime import of a separate TVM installation).

The package builds successfully with TVM-related components contained within the upstream source tree.

As a result, the recipe does not include libtvm as an external dependency.

Once this base recipe is merged, I’ll follow up with tile-kernels.

Happy to adjust if there are upstream constraints or edge cases I may have missed.

[h-vetinari]

As a result, the recipe does not include libtvm as an external dependency.

We should unvendor this, especially given that tilelang upstream documents how to do this

[1minds3t]

@h-vetinari I looked into the upstream-supported mechanism for external TVM via TVM_ROOT.

While upstream documents this as a possible workflow, they also explicitly state that:

• tilelang depends on a customized TVM submodule
• external TVM is still used in a rebuild step (TL_LIBS)
• and this approach can lead to path and ABI issues

This confirms that even upstream considers external TVM experimental for
tilelang specifically.

This indicates that TVM is not currently a cleanly separable dependency in upstream’s build system.

Given this, I believe attempting to unvendor TVM in conda-forge at this stage would result in a fragile and potentially non-reproducible package that deviates from upstream’s tested build path.

I agree that long-term this should be addressed by upstream introducing a stable, versioned TVM dependency boundary. I will open an issue with tile-ai to track this decoupling.

For this initial release, would it be acceptable to proceed with vendored TVM while we track proper separation upstream?

[1minds3t]

For additional context: TVM itself vendors multiple third-party dependencies
(OpenCL-Headers, cutlass, compiler-rt, libflash_attn) some dating back 4 years,
making a fully unvendored conda-forge chain impractical in the near term.