Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

GPL licensed ROS software stack

If a ROS software stack (that includes libraries, ROS nodes, messages and services, config files, etc) is GPL-licensed, then how much of this software stack can be used without forcing the GPL license on the whole project?

AFAIK modifying or linking with any library will force GPL license, but:

  1. Are the generated message headers also GPL-licensed ? Otherwise, every package using those message will be tainted with GPL :(
  2. As described in http://wiki.ros.org/DevelopersGuide#Licensing

    The ROS packaging and communication system allows for fine-grained licensing. Because nodes communicate via ROS messages, code from multiple nodes is not linked together. Thus the package provides a kind of "license boundary

    However, the project requires some nodes to be running (e.g linking to them in *.launch files). Wouldn't it break the GPL clause ?

GPL licensed ROS software stack

If a ROS software stack (that includes libraries, ROS nodes, messages and services, config files, etc) is GPL-licensed, then how much of this software stack can be used without forcing the GPL license on the whole project?

AFAIK modifying or linking with any library will force GPL license, but:

  1. Are the generated message headers also GPL-licensed ? Otherwise, every package using those message will be tainted with GPL :(
  2. As described in http://wiki.ros.org/DevelopersGuide#Licensing

    The ROS packaging and communication system allows for fine-grained licensing. Because nodes communicate via ROS messages, code from multiple nodes is not linked together. Thus the package provides a kind of "license boundaryboundary"

    However, the project requires some nodes to be running (e.g linking to them in *.launch files). Wouldn't it break the GPL clause ? ?