Skip to content

Conversation

@sharwell
Copy link
Contributor

@sharwell sharwell commented Nov 20, 2019

When the CUDA dependencies are installed, they are automatically copied to the output directory during builds. This change reduces cases where execution fails due to failure to find and/or load these binaries.

This change was derived from the discussion in AlturosDestinations/Alturos.Yolo#6 and seemed to work well when I was having trouble getting started.

When the CUDA dependencies are installed, they are automatically copied
to the output directory during builds. This change reduces cases where
execution fails due to failure to find and/or load these binaries.
Copy link
Contributor

@ycshu086 ycshu086 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems unnecessary if files in MSBuildExtensions were copied and CUDA_PATH was added to Environment Variables (restart required). Are we missing some steps in README.md?

@sharwell
Copy link
Contributor Author

This seems unnecessary if files in MSBuildExtensions were copied and CUDA_PATH was added to Environment Variables (restart required). Are we missing some steps in README.md?

I did all of these things.

image

... files in MSBuildExtensions were copied ...

I might have made a mistake on this step. However, it's not clear why this step is required. It seems to only apply when compiling C++ projects, but this solution only has C# projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants