26
edits
FAQ: Difference between revisions
m
→Should I favor the MEX interface to avoid the GPL?: Minor correction of grammar
m (→Will you change the license of the Octave libraries for me?: Minor grammatical error) |
m (→Should I favor the MEX interface to avoid the GPL?: Minor correction of grammar) |
||
| Line 171: | Line 171: | ||
==Should I favor the MEX interface to avoid the GPL?== | ==Should I favor the MEX interface to avoid the GPL?== | ||
'''No.''' The original reason for implementing the [https://www.gnu.org/software/octave/doc/interpreter/Mex_002dFiles.html MEX interface] for Octave was to allow Octave to run free software that uses MEX files (the particular goal was to run [https://computation.llnl.gov/projects/sundials/release-history#sundialsTB sundialsTB] in Octave). The intent was to liberate that software from Matlab and increase the amount of free | '''No.''' The original reason for implementing the [https://www.gnu.org/software/octave/doc/interpreter/Mex_002dFiles.html MEX interface] for Octave was to allow Octave to run free software that uses MEX files (the particular goal was to run [https://computation.llnl.gov/projects/sundials/release-history#sundialsTB sundialsTB] in Octave). The intent was to liberate that software from Matlab and increase the amount of free softwares available to Octave users & not to enable people to write proprietary code for Octave. For the good of the community, we strongly encourage users of Octave to release the code they write for Octave under terms that are compatible with the [https://www.gnu.org/licenses/gpl.html GPL]. | ||
==Why can't I use code from File Exchange in Octave?== | ==Why can't I use code from File Exchange in Octave?== | ||