at first, I'd like to thank the authors for providing cJSON under the MIT license which is very generous. At the same time, I'd like to apologize for the following (probably dumb) question:
I am working on a project where I would like to use cJSON by directly adding cJSON.c and cJSON.h to the makefile. That is, I wouldn't alter the cJSON sources in any way, but just include them in the makefile. In that sense, my project would only use cJSON, but cJSON would not be the main part. The outcome of my project will be a Windows DLL.
Under these conditions, what do I need to do to adhere to the license? When I pass on the compiled DLL file, do I need to bundle a text file with the cJSON license with it? Or is it sufficient to have the license at the source code level in the project (or Git repository, respectively)?
Dear all,
at first, I'd like to thank the authors for providing cJSON under the MIT license which is very generous. At the same time, I'd like to apologize for the following (probably dumb) question:
I am working on a project where I would like to use cJSON by directly adding cJSON.c and cJSON.h to the makefile. That is, I wouldn't alter the cJSON sources in any way, but just include them in the makefile. In that sense, my project would only use cJSON, but cJSON would not be the main part. The outcome of my project will be a Windows DLL.
Under these conditions, what do I need to do to adhere to the license? When I pass on the compiled DLL file, do I need to bundle a text file with the cJSON license with it? Or is it sufficient to have the license at the source code level in the project (or Git repository, respectively)?
Thank you very much in advance.