Say, I have a game engine which is meant to be an executable, not a library (i.e. it has its' own main() and has the top-level control. It calls on other libraries but cannot be used as a dynamic library).
Does it make sense to license it under the LGPL? My reasoning for this is that I want the core of the engine to be open source, but to permit using a proprietary "helper" library which is called on by the engine.
One use case I see for this: Say the engine is used for a Steam game which makes use of Steam's API. Then the API calls to the dynamic library can be put in the engine source and released. However, the actual library would remain closed sourced and proprietary.
Does this use-case of the LGPL make sense? I am clarifying because everywhere I see that the LGPL is sometimes referred to as "library GPL" and is basically used for libraries that are called by applications, not the other way around.