Nice - yeah, I figured it's fine with assets created by these apps, but with engine code you will probably have to include the license/link to the source code etc. That's ok though imo.
From the OGRE License page
Under the LGPL you may use Ogre for any purpose you wish, as long as you:
1. Release any modifications to the OGRE source back to the community
2. Pass on the source to Ogre with all the copyrights intact, or link back to a place where the source code can be obtained (e.g. this site)
3. Make it clear where you have customised it.
The above is a precis, please do read the full license agreement.
There are a few specific details to point out:
1. When OGRE is dynamically linked (the default), anything you use it in is not a derived work and thus you can license your own software under any license you choose; the LGPL does not 'infect' your software.
2. When OGRE is statically linked, your work becomes a derived work of OGRE and is covered by the LGPL too. You must either release your source, or include linkable object files of your work if you do this
3. The license mentions 'inlining' as potentially making the software using it a derived work; however this is mostly an issue for libraries which mostly comprise headers, like template libraries. Inlining in OGRE is entirely for performance and is a small part of the whole, and therefore any inlining of OGRE headers does not constitute a derived work (so point 1 still applies).
A common question is 'can I create commercial applications using OGRE under the LGPL'? The answer is an emphatic yes, provided you adhere to the license conditions, summarised above. Whilst we do make an alternative license available to those who specifically need it, it is not the case that you need this alternative license for commercial work. There are plenty of commercial applications that have used OGRE under the LGPL.
All my emphasis.