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
e.g. the C, C++, Python, and Rust files that are now checked into this repository, and in general what the license status is of source files output by Protobuf.
I am certain that GCC somewhere mentions specifically that the assembly and binaries it produces can be released under a proprietary license.
I am nearly certain the same is true for code generated by tools like Bison and flex.
Hopefully the same is true for Protobuf, but having a link to a specific section of the Protobuf documentation explaining its policy on this question would be helpful.
The text was updated successfully, but these errors were encountered:
According to Wikipedia, protobuf is licensed under the BSD License.
The license in the protobuf repository is available here, which essentially outlines the same terms as the BSD License.
For more detailed information on the BSD License, you can find the documentation here.
So, from my understanding, to summarize:
Redistribution and use in both source and binary forms, with or without modification, are permitted, but the following conditions must be met:
Redistributions of source code and binary must retain the copyright notice, conditions, and disclaimer as stated in the "BSD License documentation." The names of Google or its contributors cannot be used for endorsement without prior written consent
I was wondering whether the source code files output by the Protobuf compiler protoc might have a similar exception.
Even if they don't have such an exception, and the output source files of protoc are BSD licensed, that should be perfectly fine for including in software released under a proprietary license.
There is a note for this in the protobuf license file:
Code generated by the Protocol Buffer compiler is owned by the owner
of the input file used when generating it. This code is not
standalone and requires a support library to be linked with it. This
support library is itself covered by the above license.
e.g. the C, C++, Python, and Rust files that are now checked into this repository, and in general what the license status is of source files output by Protobuf.
I am certain that GCC somewhere mentions specifically that the assembly and binaries it produces can be released under a proprietary license.
I am nearly certain the same is true for code generated by tools like Bison and flex.
Hopefully the same is true for Protobuf, but having a link to a specific section of the Protobuf documentation explaining its policy on this question would be helpful.
The text was updated successfully, but these errors were encountered: