-
Notifications
You must be signed in to change notification settings - Fork 6.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should ISPC be a well-known tool? #26965
Comments
Thanks for posting this issue, you can add it like |
Fixing by PR #29261 |
This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 60 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment. |
This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 60 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment. |
This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 60 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment. |
I am planning on contributing the port files of OSPRay, OpenVLK and rkcommon that I have created. They depend on ISPC. I currently use
find_program
in their port files to acquire the system installed variant of it, but that will certainly not work for the vcpkg pipelines here. Therefore my question, how to best handle it? Adding it to vcpkg_find_acquire_program sounds like an option, but since ISPC is a compiler, I am not sure that is the right place (seeing that compilers are generally expected to be provided through toolchain files).See also previous issues on ISPC: #15846, #8698
The text was updated successfully, but these errors were encountered: