CMake package name conflict with `shader-slang` (`slangConfig.cmake` collision)

[JavierMatosD]

Hi! I’m one of the core maintainers for vcpkg. We have a contributor attempting to package this project and ran into a CMake package naming conflict that prevents users from installing this library alongside another project. This project installs a CMake package named: slangConfig.cmake.

However, another project in the ecosystem, shader-slang, also installs a CMake package with the same name (slangConfig.cmake). Because CMake package names are global identifiers, this makes it impossible for users to install both libraries in the same environment. Any call find_package(slang) becomes ambiguous and resolves to whichever library was installed last.

Package managers like vcpkg must follow upstream CMake package names exactly. We cannot rename or override the package name locally without breaking compatibility with upstream documentation and existing CMake projects.

To allow both libraries to coexist, we need guidance from upstream on the intended naming.

I’d appreciate your thoughts on either of these options:

1. Rename the CMake package to something unique, for example slang-verilog. This would align with Repology's naming for this project. https://aur.archlinux.org/packages/slang-verilog

2. Provide and alias package, such as installing both:

slangConfig.cmake
slang-verilogConfig.cmake

If you prefer, vcpkg can ship the alias - but only with explicit upstream approval.

How do you intend this library to coexist with shader-slang? Would you be open to renaming the CMake package or providing an alias so both can be used in the same project?

[MikePopoloski]

slang-verilog seems like a fine name to disambiguate. Shipping an aliased Config.cmake file seems easy enough. If someone wants to provide a PR I can accept it.

[dg0yt]

Apart from the identical CMake package name, both packages provide a slang::slang target.

[MikePopoloski]

I find it very unlikely anyone would ever use the two packages together in the same project, but all the same if it's a problem you can add a CMake option to change the alias target name to whatever makes sense, slang-verilog::slang maybe.

[MikePopoloski]

@JavierMatosD @dg0yt are you guys waiting on me for anything here?