> How do I install that? I downloaded a .tar.gz from there, but it's not recognized as
> either "Archive" or "Local" in Install new Software -> Add Repository.
Ok, I figured it out: it's not meant to be installed into an existing installation, it's a new installation altogether, without CDT, into which I can then install CDT for the first time.
I'm glad you got it. Let me know if there is anything else I can do to help.
Another question: is there a technical reason for us to depend on such a recent platform? Have we actually, in the few weeks since CDT's 2019-06 release, introduced uses of platform APIs that were not present in Platform 2019-06?
Short answer, yes.
I believe we decided
as a community to track CDT against latest platform earlier this year. The result of this is that I regularly bump the target file to track latest platform builds so that by release time everything is lined up nicely. Going forward this requirement is needed because we depend on latest version of, for example, LSP4E and that also tracks latest platform. Once we are building with a version of the platform, we cannot run on older versions. In other words, we must prevent being installed in any older version of platform than we built against. This latter part comes down to some subtle Java issues which means even if CDT's source code has not changed, the dependent project's changes can cause our binary code to be different, and that difference means we can't run in older versions of the dependency. See Bug 536448
for an example of what happened before we added this restriction, and gerrit
for what I do in practice to resolve issue.
I am happy to revisit the original decision as getting the balance right is very tricky. For example, it may even make sense to have different target platforms for "core"ish parts of CDT than for newer parts of CDT.
I hope that answers the question,
cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit