You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on wrapping libacc for Julia, as it is quite a bit faster than whatever I have been able to come up with. (Also, I wanted to learn how to wrapp C++ packages).
Now I have a basic wrapper working, and I am thinking about making it available to everyone. It compiles against libacc, but I also copied the vector.h and algos.h files from the MVE project you linked in #3.
I wanted to ask what kind of licensing would work for you. I have your code in a separate folder with the License.txt file from the MVE repository. Would that work for you? I am not yet sure about the License of my code, but this is in total only about 60 lines of code, so not that significant.
I also would like to give some credit in the description. I read the license as requiring me to ask you, so would it be fine for you, if I referenced this repo in the Readme and description of the wrapper repository?
Thanks for the cool library and all the best
Paul
The text was updated successfully, but these errors were encountered:
Hello,
I am working on wrapping libacc for Julia, as it is quite a bit faster than whatever I have been able to come up with. (Also, I wanted to learn how to wrapp C++ packages).
Now I have a basic wrapper working, and I am thinking about making it available to everyone. It compiles against libacc, but I also copied the
vector.h
andalgos.h
files from the MVE project you linked in #3.I wanted to ask what kind of licensing would work for you. I have your code in a separate folder with the License.txt file from the MVE repository. Would that work for you? I am not yet sure about the License of my code, but this is in total only about 60 lines of code, so not that significant.
I also would like to give some credit in the description. I read the license as requiring me to ask you, so would it be fine for you, if I referenced this repo in the Readme and description of the wrapper repository?
Thanks for the cool library and all the best
Paul
The text was updated successfully, but these errors were encountered: