licenses.. n' stuff

[JaJDoo]

so I've been working on a Frankenstein thing for a few weeks now using OGRE, Qt and betajean's beastie. i eventually want to release it as an open source software;
so i thought "if I'm gonna make it free and when i'll upload it it will be only about half done, i wouldn't really need to worry about license stuff yet".

but its the internet - that cant be a good idea...

i don't really have the slightest idea about licenses- i usually just ignore them. what license should i use? do i need to do anything other than write the license stuff on the beginning of all the files?
i gather both OGRE uses MIT (correct?) and Qt uses LGPL (correct?) .. does this raise any issues?

[haltendehand]

It doesn't raise any issues(you just need to say somewhere that Ogre and Qt were used[for example in the readme]) , and I would suggest to publish your program under the GPL or the LGPL license.

[JaJDoo]

It doesn't raise any issues(you just need to say somewhere that Ogre and Qt were used[for example in the readme]) , and I would suggest to publish your program under the GPL or the LGPL license.

something i wonder.. to "release under a license" simply means to inform the 'customer' that its under that license? no other action involved?

[haltendehand]

No, that are the conditions of MIT&LGPL

[jacmoe]

If you are dynamically linking to Qt, then you can choose whatever license you want.