I’ve recently demonstrated the the feasibility of replacing Simulink with Xcos for digital power development within my company. I officially have the go-ahead to build a custom toolbox for simulating/testing C code we use to drive control algorithms. (We will be saving a fortune!)
The potential issue is this C code is proprietary and I’ll be calling it from within blocks developed for this custom toolbox.
Questions:
- If we decide to share this toolbox with a 3rd party, would we be forced publish our source code? My understanding is Scilab is licensed under the GPL.
- Build/loads scripts within the Xcos Skeleton Toolbox appear to be licensed under BSD. If I re-purpose the existing build/load scripts, I assume I would be constrained to the terms of the BSD license? (i.e. attribution, copyright notice, etc.)
1 Like
Hi dangerfish
IMO this is an important question. I am sure others will be able to answer this.
I am no expert, but AFAIK it is true that once you use GPL software, you are forced to also share your library.
On the other hand, Scilab was prior to v. 6 licensed under CeCILL : CeCILL - Wikipedia
CeCILL might be helpful in the sense that (quote): " but it makes no claim to work that executes in “separate address spaces”, which may be licensed under terms of the licensee’s choice."
Maybe some people who are close to the Scilab project (not me) can explain in detail.
I look forward to see the proper answer to your question.
With kind regards,
Claus
1 Like
I appreciate your insight, regardless!
Hello,
This is a widespread question; we have answered it in the past with an unequivocal statement: proprietary toolboxes exist, and they have their own license 1. The Scilab license (CeCILL or GPLv2) only impacts code shipped within the Scilab executable; even examples and demo toolboxes have a BSD license.
For example, the Scilab team at 3DS delivered toolboxes for customers in the past 2 3 ; external users also developed their toolboxes 4.
Regards,
2 Likes
I appreciate the definitive answer regarding this! Thank you.