Quote: Original post by swiftcoder

Quote: Original post by Codeka
Ogre is "dual licensed". That is, for a fee you can buy a license that allows you to make modifications to the Ogre library without requiring that you release those changes (as you would be required to do if you used the LGPL license).

I can't say which version Runic used for Torchlight, but it wouldn't surprise me if they used the alternative license.

Note that the upcoming version of Ogre (already available in SVN) is licensed under the far more liberal BSD license.

On the page I linked to, it actually mentions they're switching to an MIT license, but yeah, still far more permissive than LGPL.

These types of blanket statements always make me laugh. If the GPL and LGPL were bad, they wouldn't exist.

Quote: Note that the upcoming version of Ogre (already available in SVN) is licensed under the far more liberal BSD license.

To finish that thought, the proprietary license is going away because it is no longer necessary. The MIT License only requires that you provide OGRE's copyright information and the license text with your application. The OGRE team's blog post on the subject is very interesting (well, to an open source fan like me anyway), as they believe "encouraging adoption via simpler licensing is likely to result in more contributions overall than coersion[sic] via complex and restrictive licensing does." Normally I'd disagree but with a project as big, well-known, and mature as OGRE I tend to agree, and I think it's a great move on their part.

Hmmm. Do the developers usually let you pay them to have a different license? I mean if I get funding somewhere I would be able to most likely afford something like that.

Quote: Original post by 3DModelerMan
Hmmm. Do the developers usually let you pay them to have a different license? I mean if I get funding somewhere I would be able to most likely afford something like that.

It depends on the developer. In particular, ask a developer on one of the GNU products (GCC, GTK, Emacs, etc) and you'd probably just get laughed at. For some people, the GPL is more than just a license - it's a philosophy.

Generally, if the developer is dual-licensing their product, they'll say so on their website. If not, I guess it doesn't hurt to ask...

Is it allowed to just include the DLL and then put right in the same folder as the DLL a text file that links to the download for the source code? I wouldn't want to bloat the game folder with all the source code.

Basically, that is correct. You don't have to ship the source code with the binary.

But to be thorough, the license says you have to make it relatively easy to obtain and build the source code to produce the exact DLL that you provided. You will probably be perfectly fine just linking to OGRE's source download page as well as the page with build instructions, assuming you won't be making any changes. If you do make changes, you are required to provide your own full download of the modified version (you cannot only provide diffs, though they might be welcome as an alternative).

Also note that the source doesn't have to be publicly available, as long as the binaries aren't publicly available. You only need to provide a link to the people that receive the binary.