You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m looking to understand how we want to support the use of hipfort in the CMake build system. Currently, I’m finding that I have to set FC, CC, and CXX all equal to hipfc in order to build an application that depends on hipfort.
Further, when building distributions for multiple hardware vendors, it’s not clear how to specify the target hardware (—offload-arch does not work to build for nvidia hardware when nvidia hardware is not present).
I’m looking for some guidance on how we should be incorporating hipfc into CMake build systems and how to specify target architectures, even when the target architecture is not present on the build platform.
The text was updated successfully, but these errors were encountered:
A set of hipfort CMAKE library targets would certainly be nice! Something that would do hipfc's job of linking to either CUDA or AMD libaries so we aren't forced to use hipfc.
It is not great to have to pass --offload-arch to hipfc in order for it to compile for a CUDA backend. The environment variable $HIP_PLATFORM should be all that is requried.
I’m looking to understand how we want to support the use of hipfort in the CMake build system. Currently, I’m finding that I have to set FC, CC, and CXX all equal to hipfc in order to build an application that depends on hipfort.
Further, when building distributions for multiple hardware vendors, it’s not clear how to specify the target hardware (—offload-arch does not work to build for nvidia hardware when nvidia hardware is not present).
I’m looking for some guidance on how we should be incorporating hipfc into CMake build systems and how to specify target architectures, even when the target architecture is not present on the build platform.
The text was updated successfully, but these errors were encountered: