Hello Marc-Andre,
This is big and quite hot topic: Oomph , .target and who is the king
of the hill.
With the current resource constraints I would suggest the following:
1) we are maintaining CDT.setup to let potential contributors
configure the CDT workspace easily
https://git.eclipse.org/r/#/c/154525/
2) we are using .target files for CDT releng and keep them in sync
with .setup manually at the moment
in progress
3) we are discussing in background the best way to reduce
duplication between .setup and .target files
let's create another topic for "cross-project-issues-dev" and
discuss it there
Regards,
AF
17.12.2019 6:16, Marc-Andre Laperle
пишет:
Hi
Johna,
Thanks for doing this. There are a lot
of new steps I didn’t know about. I like the
GitHub checkboxes for this. It would be
interesting to see if some of those steps could be
automated or dropped eventually. Like:
- Do we still need Oomph? It’s broken
most of the time and it’s a drag to maintain. I’ve
never really been comfortable with generating the
.target file from .setup file either. I would
rather prefer doing it the other way around and
not have the CDT build depend on Oomph.
CDT build does not currently depend on
Oomph - the cdt.setup and cdt.target are both
independently manually maintained - I have not been
doing that well as I kept forgetting to update
cdt.setup. Alexander Fedorov is quite keen to see the
Oomph flow work and has just been in the process of
contributing fixes, see Bug 558288.
Sorry I didn’t phrase that clearly. I know the build
*currently* does not depend on Oomph that that both files are
independent. But I know there is a way to have the .target
generated from the .setup but never wanted that because it
meant the CDT build would depend on Oomph. Having the .setup
generated from the .target would be more acceptable IMO.
If there is a way to make cdt.setup
generated from cdt.target that would be great.
Alexander, do you perhaps know a way? Can the
cdt.setup just point at cdt.target file instead of
having to be duplicated?
- Can we configure eclipserun to use
the same target platform as the rest of the
build now? (Well it actually used to be like
that at the very beginning but it got changed in
Tycho)
I found it quite stark how many manual
steps I am actually doing every three months for a
release - and so far I have not properly added
endgames for the secondary components like
cdt-gdb-adapter, launchbar, etc. So any automation
is a good idea.
Marc-André
Hello folks,
I have started updating
CDT's release engineering
documentation to properly reflect what
I am doing and to make sure I don't
forget anything. It has become
significantly more complicated in the
past few years as we have added
additional plug-in projects (launchbar
and tools.template) and the more
recent addition of Node & VS Code
plug-ins.
Please let me know if
this works for you all or if you have
any concerns.
Thank you,
Jonah
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve
your password, or unsubscribe from this
list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options,
retrieve your password, or unsubscribe from this list,
visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
|
