Hi, Ansgar,
A question that I have is, what is the specific affinity of this library with Designer? It’s simply (today) a collection of primitive types as recognized in the ANSI C standard.
This library seems to me a good candidate for a new Papyrus Model Repository project after the fashion of the UPR project (which is dedicated to providing OMG-standard profiles, so not appropriate for our purposes). I am not sure, but I feel like the notion of a common provider of shared model libraries has been discussed before. If not, perhaps we should start that discussion now.
cW
On 6 April, 2016 at 11:25:46, Ansgar Radermacher (ansgar.radermacher@xxxxxx) wrote:
Hi Peter,
the first release of designer is planned for Friday morning.
I talked to Francois (in CC) who knows build issues much better
than I do: I understand that it is possible to declare additional
repositories in the Papyrus-RT update site configuration. These are
searched automatically when the user installs Papyrus-RT. I.e. the
user does not have to add further update sites manually.
Thus, the main issue is an additional configuration in the
build/update site of Papyrus-RT. While it may seem a certain
additional effort for a small library, it will keep the possibility
open to have more common code in the future (e.g. the reverse
mechanisms)
The two alternatives are (1) keeping a separate copy (that might
involve independently) and (2) keeping the Ansi C library in the
Papyrus repository (and remove it from designer). Both options are
in my opinion less good.
Best regards
Ansgar
On 06/04/2016 15:48, Peter Cigéhn wrote:
Hi,
When being reminded about
the move of the C++ code generator from Papyrus Extras to its own
repository, I wonder about move in p2 repos.
As discussed before, we
did not want that end-users of Papyrus-RT should be forced to bring
along anything else than the AnsiCLibrary itself. But if we now
move the C++ code-generator into its own repo, do that mean that we
also will move stuff into separate p2 repos?
As it has been so far, is
that the plugin with the AnsiCLibrary has been installed "for free"
since the user simply used the aggregated apyrus repo (which
included both Maind and the Extras repos). But if we now move stuff
into own repositories, do that also impact this?
Will we be forced into
having an additional p2 repo, just for the purpose of getting
in the AnsCLibrary? If that is the case, then maybe the placement
of the AnsiCLibrary could be questioned.
Ansgar, can you please enlighten us regarding this so that we
understand the conseqeunces from an end-user perspective installing
Papyrus-RT directly from p2 repos.
/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
--
Ansgar Radermacher CEA/DRT/DILS/LISE
http://www-list.cea.fr/index.htm
phone: +33 16908 3812
mailto: ansgar.radermacher@xxxxxx
_______________________________________________
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
|