Home » Language IDEs » C / C++ IDE (CDT) » Eclipse 3.0M3 and CDT
| Eclipse 3.0M3 and CDT [message #79888] |
Sun, 07 September 2003 14:25  |
Eclipse User |
|
|
|
Originally posted by: crusader.far-galaxy.de
I've tested the Eclipse 3.0M2 whith CDT it works correctly for me,
but after updating 3.0M2 to 3.0M3 the c editor refused to open cpp files.
Does anyone know how to fix this?
Thanks in advance
Sebastian
|
|
|
| Re: Eclipse 3.0M3 and CDT [message #79949 is a reply to message #79888] |
Mon, 08 September 2003 20:02  |
| Eclipse User |
|
|
|
Originally posted by: dschaefe.ca.ibm.com
There has been an API change (unfortunately internal) that has broken the
CDT Editor for 3.0M3. Right now, I'm not sure how to fix this...
Doug
"Sebastian Fohler" <crusader@far-galaxy.de> wrote in message
news:bjfei1$9i9$1@eclipse.org...
> I've tested the Eclipse 3.0M2 whith CDT it works correctly for me,
> but after updating 3.0M2 to 3.0M3 the c editor refused to open cpp files.
> Does anyone know how to fix this?
>
> Thanks in advance
> Sebastian
|
|
|
| Re: Eclipse 3.0M3 and CDT [message #80485 is a reply to message #79949] |
Wed, 17 September 2003 19:58 |
| Eclipse User |
|
|
|
Originally posted by: jmricker.eos.ncsu.edu
"Doug Schaefer" <dschaefe@ca.ibm.com> wrote in
news:bjin6k$75r$1@eclipse.org:
> There has been an API change (unfortunately internal) that has broken
> the CDT Editor for 3.0M3. Right now, I'm not sure how to fix this...
>
> Doug
>
> "Sebastian Fohler" <crusader@far-galaxy.de> wrote in message
> news:bjfei1$9i9$1@eclipse.org...
>> I've tested the Eclipse 3.0M2 whith CDT it works correctly for me,
>> but after updating 3.0M2 to 3.0M3 the c editor refused to open cpp
>> files. Does anyone know how to fix this?
>>
>> Thanks in advance
>> Sebastian
(Windows XP, Eclipse 3.0)
Is this problem also responsible for this problem: I'm new to Eclipse so
I've downloaded Eclipise 3.0. I used Help -> Software Updates -> Find and
Install to install CDT and used
http://update.eclipse.org/tools/cdt/updates/release as the update URL.
When I select and add the Windows CDT plugin, I get an error saying:
Eclipse C/C++ Development Tools (Windows) (1.1.0): Update conflict
detected (see details). Please deselect this update and try again.
Eclipse C/C++ Development Tools (1.1.0): Feature requires plug-in
"org.eclipse.platform (2.1.0)", or compatible.
Eclipse C/C++ Development Tools (1.1.0): Feature requires plug-in
"org.eclipse.platform (2.1.0)", or compatible.
Sounds like if I want to use CDT, I'll need to remove Eclipse 3.0 and go
back to a version <=2.1.0? Any way around this?
Thanks
Jody
|
|
|
| Re: Eclipse 3.0M3 and CDT [message #81173 is a reply to message #80485] |
Fri, 26 September 2003 17:15 |
| Eclipse User |
|
|
|
Originally posted by: dschaefe.ca.ibm.com
Unfortunately, yes. CDT 1.1 and CDT 1.2 will only work on Eclipse 2.1 and
not on Eclipse 3.0 M3 and later. Equally unfortunately, there doesn't
appear to be a quick workaround in the code of the CDT to address this.
Luckily, it is possible to have as many copies and versions of Eclipse
installed in a machine at one time so you won't have to remove 3.0.
We will be working early in the next release of CDT 2.0 to get up and
running on Eclipse 3.0. This should happen by Eclipse 3.0 M5 and earlier in
the CDT nightly builds.
Doug
"Jody" <jmricker@eos.ncsu.edu> wrote in message
news:Xns93F9A2BB94D8Anoemailnonenone@204.138.98.10...
> "Doug Schaefer" <dschaefe@ca.ibm.com> wrote in
> news:bjin6k$75r$1@eclipse.org:
>
> > There has been an API change (unfortunately internal) that has broken
> > the CDT Editor for 3.0M3. Right now, I'm not sure how to fix this...
> >
> > Doug
> >
> > "Sebastian Fohler" <crusader@far-galaxy.de> wrote in message
> > news:bjfei1$9i9$1@eclipse.org...
> >> I've tested the Eclipse 3.0M2 whith CDT it works correctly for me,
> >> but after updating 3.0M2 to 3.0M3 the c editor refused to open cpp
> >> files. Does anyone know how to fix this?
> >>
> >> Thanks in advance
> >> Sebastian
>
> (Windows XP, Eclipse 3.0)
>
> Is this problem also responsible for this problem: I'm new to Eclipse so
> I've downloaded Eclipise 3.0. I used Help -> Software Updates -> Find and
> Install to install CDT and used
> http://update.eclipse.org/tools/cdt/updates/release as the update URL.
> When I select and add the Windows CDT plugin, I get an error saying:
>
> Eclipse C/C++ Development Tools (Windows) (1.1.0): Update conflict
> detected (see details). Please deselect this update and try again.
> Eclipse C/C++ Development Tools (1.1.0): Feature requires plug-in
> "org.eclipse.platform (2.1.0)", or compatible.
> Eclipse C/C++ Development Tools (1.1.0): Feature requires plug-in
> "org.eclipse.platform (2.1.0)", or compatible.
>
> Sounds like if I want to use CDT, I'll need to remove Eclipse 3.0 and go
> back to a version <=2.1.0? Any way around this?
>
> Thanks
> Jody
>
|
|
|
| Re: Eclipse 3.0M3 and CDT [message #82084 is a reply to message #81173] |
Sat, 04 October 2003 04:57 |
 Jean-Christophe Deprez
Messages: 133
Registered: July 2009 |
Senior Member |
|
|
if you think about it, sticking with eclipse 2.1 is not good strategy.
since cdt is a 'bleeding-edge' technology, the type of person who is
willing to try it and use it is (obviously) someone who wants to learn
about/use bleeding edge technology. probably almost all eclipse users
who fit into this category are using eclipse 3.0, because it too is
bleeding-edge. since cdt does not work with 3.0, these users are not
using cdt.
conversely, it is reasonable to assume that many who use eclipse 2.1
instead of 3.0 do so because it is stable, 'tried and true' technology.
these people use 2.1 specifically because it is not likely to have bugs
which will cause them to lose work/productivity, and because the
procedure for accomplishing any particular task with 2.1 is the same as
it was yesterday and will be the same tomorrow. these people are
extremely unlikely to be interested in using cdt because it is still too
'bleeding edge' for them.
in short, the policy of developing cdt only for eclipse 2.1 is probably
severely limiting the number of people who are willing to test it. since
*contributers* in open-source projects are always people who first
use/test the product and become excited about it, this policy severely
limits the number of potential cdt contributers. it is likely some of
these potential contributers are very talented, and would be a great
boon to the cdt development effort. cdt will never get these
contributers, because they can not use cdt.
although i am interested in the concept of a unified ide, i do not use
cdt precisely because it does not work with eclipse 3.0. i do not have
the time or inclination to run two separate versions of the same ide
just to try one product. i instead put my efforts into the dev-cpp ide
(www.bloodshed.org). i'm sure there are many others like me.
does this make sense?
alvin
|
|
| |
| Re: Eclipse 3.0M3 and CDT [message #82141 is a reply to message #82084] |
Mon, 06 October 2003 00:37 |
| Eclipse User |
|
|
|
Originally posted by: ed.burnette.REMOVE.THIS.sas.com
Personally I agree, and I had to stop using CDT for the same reason. The
Eclipse plain text editor and external tool launches for builds had to
suffice. Fortunately, development for the next version of CDT will be
starting soon and will be based on Eclipse 3.
--
Ed Burnette, co-author Eclipse in Action (www.manning.com/gallardo)
"Alvin Thompson" <nobody@nowhere.com> wrote in message
news:3F7E5350.4070808@nowhere.com...
> although i am interested in the concept of a unified ide, i do not use
> cdt precisely because it does not work with eclipse 3.0. i do not have
> the time or inclination to run two separate versions of the same ide
> just to try one product. ...
|
|
|
| Re: Eclipse 3.0M3 and CDT [message #83153 is a reply to message #82084] |
Wed, 15 October 2003 15:31 |
| Eclipse User |
|
|
|
Originally posted by: dschaefe.ca.ibm.com
The CDT is currently integrated into commercial products and we have to take
that into account. For CDT 1.2, there is a need to maintain the connection
with Eclipse 2.1.x. CDT 2.0, on the other hand, will line up with Eclipse
3.0. We just need to figure out the right timing to make the cutover.
Doug.
"Alvin Thompson" <nobody@nowhere.com> wrote in message
news:3F7E5350.4070808@nowhere.com...
> if you think about it, sticking with eclipse 2.1 is not good strategy.
>
> since cdt is a 'bleeding-edge' technology, the type of person who is
> willing to try it and use it is (obviously) someone who wants to learn
> about/use bleeding edge technology. probably almost all eclipse users
> who fit into this category are using eclipse 3.0, because it too is
> bleeding-edge. since cdt does not work with 3.0, these users are not
> using cdt.
>
> conversely, it is reasonable to assume that many who use eclipse 2.1
> instead of 3.0 do so because it is stable, 'tried and true' technology.
> these people use 2.1 specifically because it is not likely to have bugs
> which will cause them to lose work/productivity, and because the
> procedure for accomplishing any particular task with 2.1 is the same as
> it was yesterday and will be the same tomorrow. these people are
> extremely unlikely to be interested in using cdt because it is still too
> 'bleeding edge' for them.
>
> in short, the policy of developing cdt only for eclipse 2.1 is probably
> severely limiting the number of people who are willing to test it. since
> *contributers* in open-source projects are always people who first
> use/test the product and become excited about it, this policy severely
> limits the number of potential cdt contributers. it is likely some of
> these potential contributers are very talented, and would be a great
> boon to the cdt development effort. cdt will never get these
> contributers, because they can not use cdt.
>
> although i am interested in the concept of a unified ide, i do not use
> cdt precisely because it does not work with eclipse 3.0. i do not have
> the time or inclination to run two separate versions of the same ide
> just to try one product. i instead put my efforts into the dev-cpp ide
> (www.bloodshed.org). i'm sure there are many others like me.
>
> does this make sense?
> alvin
>
|
|
|
| Re: Eclipse 3.0M3 and CDT [message #83541 is a reply to message #83153] |
Sun, 19 October 2003 12:16 |
Steven Buroff
Messages: 119
Registered: July 2009 |
Senior Member |
|
|
I would vote for ASAP.
Steve
"Doug Schaefer" <dschaefe@ca.ibm.com> wrote in message
news:bmjp82$djl$1@eclipse.org...
> The CDT is currently integrated into commercial products and we have to
take
> that into account. For CDT 1.2, there is a need to maintain the
connection
> with Eclipse 2.1.x. CDT 2.0, on the other hand, will line up with Eclipse
> 3.0. We just need to figure out the right timing to make the cutover.
>
> Doug.
>
> "Alvin Thompson" <nobody@nowhere.com> wrote in message
> news:3F7E5350.4070808@nowhere.com...
> > if you think about it, sticking with eclipse 2.1 is not good strategy.
> >
> > since cdt is a 'bleeding-edge' technology, the type of person who is
> > willing to try it and use it is (obviously) someone who wants to learn
> > about/use bleeding edge technology. probably almost all eclipse users
> > who fit into this category are using eclipse 3.0, because it too is
> > bleeding-edge. since cdt does not work with 3.0, these users are not
> > using cdt.
> >
> > conversely, it is reasonable to assume that many who use eclipse 2.1
> > instead of 3.0 do so because it is stable, 'tried and true' technology.
> > these people use 2.1 specifically because it is not likely to have bugs
> > which will cause them to lose work/productivity, and because the
> > procedure for accomplishing any particular task with 2.1 is the same as
> > it was yesterday and will be the same tomorrow. these people are
> > extremely unlikely to be interested in using cdt because it is still too
> > 'bleeding edge' for them.
> >
> > in short, the policy of developing cdt only for eclipse 2.1 is probably
> > severely limiting the number of people who are willing to test it. since
> > *contributers* in open-source projects are always people who first
> > use/test the product and become excited about it, this policy severely
> > limits the number of potential cdt contributers. it is likely some of
> > these potential contributers are very talented, and would be a great
> > boon to the cdt development effort. cdt will never get these
> > contributers, because they can not use cdt.
> >
> > although i am interested in the concept of a unified ide, i do not use
> > cdt precisely because it does not work with eclipse 3.0. i do not have
> > the time or inclination to run two separate versions of the same ide
> > just to try one product. i instead put my efforts into the dev-cpp ide
> > (www.bloodshed.org). i'm sure there are many others like me.
> >
> > does this make sense?
> > alvin
> >
>
>
|
|
|
Goto Forum:
Current Time: Thu Dec 26 19:29:15 GMT 2024
Powered by FUDForum. Page generated in 0.03876 seconds |
] 
Search
Help
Register
Login
Home
