Hi, I had a look. Looks simple enough but the control file needs one change at least.
On Sun, Feb 11, 2024 at 03:40:43PM -0700, Cordell Bloor wrote: > hipify is a set of tools to convert CUDA sources into HIP sources. It > provides hipify-clang, which uses a clang-based parser and can therefore > translate complex C++ constructs, but requires complete input sources, > including access to any CUDA headers used. For cases where this is not If CUDA headers are a necessity then the section for hipify-clang needs to be contrib/devel, not devel. That's for free software that has dependencies on non-free software. Also, it should have a dependency on nvidia-cuda-dev. Unless its reasonable to assume CUDA users to get their headers otherwise but even in that case the section needs to be contrib/devel. > possible, it provides hipify-perl, which uses a simple perl-based parser hipify-perl is fine with regular devel section. Either package didn't include any documentation and there's no -doc package, which isn't really ideal. There is the docs directory and it could be used, but even without going for it I would suggest a README.Debian with a note about documentation being available at https://rocmdocs.amd.com/projects/HIPIFY/en/latest/. Strictly optional but something I'd like to see: Have an example .cu file to use hipify on to test the package. Can any of the unit test files serve the purpose?
