| Re: [papyrus-rt-dev] Architecture issue on uml library of the runtime |
|
Hi Peter, Good, we are in sync then! This is exactly where I would like to go with the architecture. I would like to have the current runtime service library not included
directly in the core, but in the CPP part of the tool. o.e.prt.core.cpp is the core support for the C++ language in Papyrus-RT (default language, specification of the C++ primitive types, etc.) and that one should
be dependent from the rts plugin. A new Papyrus-RT cpp feature should be setup, not included in Papyrus-RT main feature. It should be easy to reach or install such a feature, either with oomph
setup of a kind of discovery site as in Papyrus. This Papyrus-RT cpp feature should deploy the o.e.prt.core.cpp plugin, the rts library if C++ dependent and all required tooling/runtime/codegen for C++ additions. There is currently an issue, where the Papyrus-RT feature deploys by default the Papyrus-RT cpp plugins. And I have build issues when I try to integrate also
the runtime services. Regards, Rémi ------------------------------------------------------- Rémi SCHNEKENBURGER +33 (0)1 69 08 48 48 CEA Saclay Nano-INNOV Institut CARNOT CEA LIST De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Peter Cigéhn 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 On 17 March 2016 at 10:24, SCHNEKENBURGER Remi 211865 <Remi.SCHNEKENBURGER@xxxxxx> wrote:
|
