Hi Peter, Hi Christian,
as Peter already stated, there should be no dependency on the CEA
C++ profile, but only on the library. We were quite careful that
this library does not depend on the code generator. The library
itself does not even depend on Papyrus. A separate library.ui
plugin registers the library with the Papyrus extension point.
Please note that we are about to remove the C++ library from the
extras plugins for neon, as tracked in Bug 486820
(if it wasn't for merge problems this would already have been
done). The C++ library is now in a separate repository
(org.eclipse.papyrus-designer) and is called
org.eclipse.papyrus.designer.languages.cpp.library.
Please tell me, if we should delay the deletion.
Best regards
Ansgar
On 06/04/2016 14:39, Christian Damus wrote:
Hi, Peter,
I imported the
C++ extra from the Papyrus setup in an attempt to get that model
library. Anything else that it brought in would be incidental.
I don’t actually know that anything else is required; I didn’t
mean to suggest that, sorry.
BTW, I’m trying my Gerrit patch again with the ComputerSystem
model commented out of the codegen test case, tracked by bug
491150.
On 6 April, 2016 at 08:28:04, Peter Cigéhn (peter.cigehn@xxxxxxxxx)
wrote:
Hi,
I get a
bit confused about
these dependencies to the C++ code-generator in
Papyrus Extras.
Earlier when we decided which C++ primitive types
library that
should be used, some refactoring was made to reduce
the
dependencies, and ensure that the plugin containing
the
AnsiCLibrary (which was the library decided to be used
for
Papyrus-RT) was "stand-alone", and that it should not
bring along
any additional stuff from the C++ code generator in
Papyrus Extras
(since we want to avoid those dependencies, users of
Papyrus-RT
should not have to install any of the other stuff from
the C++
code-generator in Papyrus Extras).
Please
not also that it
should *only* be the AnsiCLibrary that we shall depend
on (in the
org.eclipse.papyrus.cpp.profile plugin), and not the
C++ profile.
For Papyrus-RT it should only be the RTCppProperties
profile that
shall be used to control the generated C++ code from
Papyrus-RT.
But
maybe the dependencies
you are talking about here is only within a developer
workspace,
and not the final dependencies between the resulting
plugins.
/Peter
Cigéhn
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
--
Ansgar Radermacher CEA/DRT/DILS/LISE
http://www-list.cea.fr/index.htm
phone: +33 16908 3812
mailto: ansgar.radermacher@xxxxxx
|