Skip to content
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

Getting Started Guide #3

Open
MathiasMagnus opened this issue May 15, 2020 · 0 comments
Open

Getting Started Guide #3

MathiasMagnus opened this issue May 15, 2020 · 0 comments

Comments

@MathiasMagnus
Copy link
Collaborator

@bashbaug seems to be a little shy opening issues for content discussion, so allow me to take initiative.

Following Ben's comment on needing some Getting Started Guide (and we definitely do), let's start discussing that. He already brought up two sources to dig into.

And I would like to tune in with my half-baked:

I'm not sure what's the an optimal / reasonable amount of ground we should cover. I can easily finish the Windows part and cover installing compilers (MSVC and LLVM), minimal compilation from the command-line, installing IDEs (VS and VS Code), setting them up for OpenCL development. Making a similar guide for Ubuntu isn't hard either.

I too think we should follow the Vulkan Guide and stick to Markdown for its simplicity. (Not to mention not having to convert my Primer and OpenCL-KernelLoad markdowns as well, but also SimpleOpenCLSamples has a fair amount of .md)

(Note: I shamelessly promoted consuming the OpenCL SDK from a package manager, and I intend to keep doing that. (If someone has guides to consuming OpenCL headers from Conan, please drop those into the guide too.) If this SDK is going to become a living thing and we'll expose facilities for projects to consume, apt install libopencl-icd-dev will only get us as far as users occasionally having 2 year old dependencies. )

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

No branches or pull requests

1 participant