[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
I updated the EPP fork that I used in the past, and the build passed, I was able to create the new packages for 2020-03 with 5.1.1.
I tried to figure out what would be the next step, but could not find a clear answer.
As it is now, the EPP configuration I use is a slightly changed epp.package.cpp where I added the GME features and some small branding fixes.
The first thought was to create a new configuration (epp.package.embedcpp?) and apply the changes there.
Copy/paste for the three projects would probably not be difficult, but maintaining it in sync with future changes in the .cpp projects will.
Also considering the future SimRel integration, what would be the proper solution? Ideally the .embedcpp would inherit from .cpp and change a few things, but I'm not sure such a configuration is possible.
I am tempted to stick to the current EPP fork solution, and for the moment focus on the changes to run the build on Jenkins, so I can sign the resulting packages and publish them on the download servers.
Another issue: I don't know how to handle the location of the released packages. Ideally this location would not change after joining SimRel, but this might not be possible.
Is it ok to publish the results on something like 'https://download.eclipse.org/embed-cdt/packages/2020-03/'?
Alexander, any thoughts?
Thank you,
Liviu
