[Documentation]: Add information that building on Windows is not supported #3416
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per https://rocm.docs.amd.com/projects/install-on-windows/en/develop/conceptual/release-versioning.html#windows-builds-from-source building on Windows is not supported.
This PR adds this information to the build docs, improving this information's visibility.
Fixes #3414 (comment)
References:
"The windows release cycle differs from the linux release cycle. For more information, see https://rocm.docs.amd.com/projects/install-on-windows/en/develop/conceptual/release-versioning.html The list is not up to date with the linux releases, but currently 5.7 is the latest windows release, so rocm 6.0 is not officially supported on windows. @Sabrewarrior it is sadly not possible to build rocm for windows from source, as it is not completely open source"
Originally posted by @MKKnorr in ROCm/ROCm#2729 (reply in thread)
"@ColorfulShire I agree, that this information is not very visible. As for adding a note to the build documents, I can't really do much about that, but feel free to open an issue at https://github.com/ROCm/HIP or even a PR to its documentation"
Originally posted by @MKKnorr in ROCm/ROCm#2729 (reply in thread)