Hi,
I am not sure I understand the build aspect. You say that "the build of core or the core.cpp somehow include the build of the o.e.p.rts plugin". Well, I am not sure about this about core. I expect that it should be possible to install Papyrus-RT without the C++, run-time and code-gen features, and only have core, e.g. if you only are using Papyrus-RT for structure modeling (and are not interested in the behavior modeling with state machines, and any of the code-generation stuff).
Actually, I would like to remove the dependency from the top level Papyrus-RT Feature to the Papyrus RT Core C++ Feature which we currently have (and possibly renamed it into Papyrus RT Language C++ or something)
The top level Papyrus-RT Feature should only depend on the Papyrus RT Core, Papyrus RT Profile and Papyrus RT Tooling.
The run-time and the code-generator are separate from the top level Papyrus-RT feature, and I guess the C++ language specific feature should be the same. The generic language framework should of course be included in core, but the extension on top of it (including the dependency to the run-time model library, which potentially could be language dependent).
Whenever we add additional languages in the future (Java, Alf, C) then you should be able to select only the language(s) you actually want to use. You shall not be "forced" to get C++ (as you do now if you select to install the top level Papyrus-RT feature).
Or do you foresee that we shall handle this differently regarding how to install the "optional" features of Papyrus-RT, for the use cases where only structure modeling is being used?
/Peter Cigéhn