Well, at this point s...@home is all GPL code unless we agree to release it under a different license. We also use ASMLIB, but that is neither required nor irreplaceable. In order to release s...@home under a different license we would need to remove the FFTW and ASMLIB related portions of the code.
Regarding the CUDA libraries, you could make a strong case that they are part of the operating system of the GPU, because the GPU can't be used without them. Even if that isn't the case, the libraries are shipped with any compiler capable of compiling the CUDA code (which is the other exception written into the license), so if you have the compiler then you have the ability to compile the code and you have the ability to run the code (both of which are the main point of the GPL). Essentially it's the same reason that it's legal to link to MSVCRT.DLL. If this weren't the case it wouldn't be possible to use CUDA, OpenCL, Cg, or most any GPU language in GPL code. I have questioned whether BOINC should be shipping the cuda DLLs with the apps, or whether apps should be using the ones shipped with BOINC or the ones installed with the drivers. But that's not really a GPL issue. Eric _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
