-
Notifications
You must be signed in to change notification settings - Fork 8
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
Could I make a PR for using Meson Builder? #14
Comments
Hi Átila @AtilaSaraiva, thanks for the kind feedback, I'm glad you've found it useful! |
Of course, I will start working on it as soon I finish the paper I am writing. I'll let you know once I start the hands on phase. |
Hello again! I got too excited and started working on it last night, and I came across a problem. I can compile the library just fine, but all the tests and examples use the
which results in a limitation that the command has to be run inside the folder on which the fclKernels.cl file is, otherwise the symbol name in the resulting object will have a name with the full path, which the current function written at Focal_utils.f90 cannot handle. Now comes a question, how feasible it is to addapt the code to handle any symbol name with path or not? thx for your time. |
#15 Published! please take a look 👯♂️ |
Hello again! Is it possible to us to have some sort of direct communication? I'd like to discuss some ideas for the project. Here is my personal email: atilasaraiva@gmail.com |
Hello good sir,
I love your project, as it makes opencl significantly easier to work with, competing directly with the likes of cuda, sycl, and rocm-hip.
I'd like to start using it heavily on my research, but it would be too much of a hassle to use makefiles. It would be nice if I could just use your repository as a Meson subproject. It will import all of the library, and the compiler flags will then be handled automaticaly. It is a genius piece of work.
Of course I can always make a fork and maintain it in parallel, but it would only undermine your efforts, so I looking for the collaboration route.
Thx for your brilliant work!
The text was updated successfully, but these errors were encountered: