I submitted a fix here: https://git.eclipse.org/r/#/c/132465/Thanks for updating the target and for the update site!
My updating target platform to newer tools.template broke the standalone debugger part of the build. I will resolve that as soon as possible.
Thanks, > Ah, I have own target and it works fine with the latest template build. I guess the cdt.target needs to be updated.
BTW we don't pull from Jenkins latest anymore because that caused real problems in the last year, mostly when the JIPP kept being down, but also because different branches were pulling from the same "latest" so there was strange reproduciblily issues. If any ongoing works starts on tools.template I would be glad to update things to make sure that we are not constantly having to update the cdt.target.
Jonah
Ah, I have own target and it works fine with the latest template build. I guess the cdt.target needs to be updated.
Sent from my BlackBerry - the most secure mobile device - via the Rogers Network
We pull the template plug-ins from Jenkins. Seems to be working now that I ran all the builds today.
Sent from my BlackBerry - the most secure mobile device - via the Rogers Network
This change alone will not fix it, there needs to be a new update site containing the fix in o.e.tools.template.
Marc-André
And it is. I’ve submitted M-A’s gerrit. Fetch the cdt.target, or apply the same change to yours.
D.
Yup, seeing the same. We have a gerrit open with a potential fix that Marc-Andre submitted. Basically, we’re missing com.sun.xml.bind from the target. I’m testing now whether that’s actually it.
When I try to use the CDT and create a new Core Build project (meson or standard make), hitting the Finish button does nothing and the dialog sits there indefinitely. If I use an old Managed Build project, it works ok when I create a Managed Make project.
Everything works if I use a Java 8 JVM.
Has anybody else tried this and seeing the same thing?
I see this both using the new 2018-12 M2 CPP EPP and starting up the CDT as a child Eclipse Application with all of CDT checked out in my workspace. Unfortunately, my Java debugger also froze in the parent Eclipse so I didn't get to step through the Wizard.
When I initially debugged and paused all threads, I found that the dialog was sleeping. I didn't notice anything holding locks that another thread was waiting for.
_______________________________________________
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@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev
|