Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Compiler errors in latest master

https://git.eclipse.org/r/#/c/63688/


From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Doug Schaefer [cdtdoug@xxxxxxxxx]
Sent: Wednesday, 06 January 2016 4:03 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Compiler errors in latest master

Agreed. It would be good to have two for some time. But the one for the current release should be clearly labeled as that. We can make a copy of it at the end of the previous release and keep it around until it no longer builds.

I guess my main point is that it shouldn't be labeled with the Eclipse Platform release. We depend on more than the platform these days. It is really the 'cdt.target' file. And when we save the one for a given release, it should be named that, cdt-8.8.target. IMHO.



On Wed, Jan 6, 2016 at 3:51 PM, Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx> wrote:
I don't need to support older platform personally and I'm not against supporting only one platform. Forcefully dropping the previous one is a bit odd but if that's the direction you want to go that's OK. But it can be useful to have two for some time. For example, in July, you don't necessarily want to go to next Eclipse version right away since it's quite unstable so you can have both side by side for a few months.

Marc-Andre


From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Doug Schaefer [cdtdoug@xxxxxxxxx]
Sent: Wednesday, 06 January 2016 3:12 PM

To: CDT General developers list.
Subject: Re: [cdt-dev] Compiler errors in latest master

We should really have one main target file that represents the current release, in this case Neon. We can have ones for older platforms if that helps people, but we should be clear what these are. 

As the platform and Orbit grows and gets new features and as CDT does, I expect CDT to get back to the mode of only supporting the current platform release. For those that need CDT to support older platforms, you should really be back porting what you need to the CDT branches that support those releases.

Just my opinion, and generally what I put into practice. If anyone is going to break CDT compatibility with old releases it's going to be me as I try and push CDT forward.
Doug.

On Wed, Jan 6, 2016 at 1:04 PM, Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx> wrote:
The old targets used to work and were useful for testing things with older platforms. Then there was some incompatibility because for the Eclipse 4 CSS usage but that was just one line to comment. Now there are many more incompatibilities so I think it's fair to say that keeping the old broken targets hurts more than it helps. So I think they should be removed.

The cdt-eStaging target was meant to be whatever the next Eclipse version is but we now have cdt-e4.6 so I think the term 'staging' is just causing confusion so I think it can be removed as well.

That should just leave cdt-e4.6, the only working one right now. Note that in the future, we might have more than one working target, depending on changes in the platform and whether or not CDT adopts some new APIs.

Marc-Andre


From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Doug Schaefer [cdtdoug@xxxxxxxxx]
Sent: Tuesday, 29 December 2015 12:44 AM

To: CDT General developers list.
Subject: Re: [cdt-dev] Compiler errors in latest master


On Dec 29, 2015 12:13 AM, "Jonah Graham" <jonah@xxxxxxxxxxxxxxxx> wrote:
>
> Hi Justin,
>
> the CDT master branch is the active development branch for Eclipse Neon which is version 4.6, scheduled for release in June, but already on Milestone 4. (The CDT version BTW is 9.0). Therefore to get the correct versions of the dependencies, you need to use cdt_e4.6.target.
>
> If you want to edit the CDT that is part of Mars.1 (version 4.5.1), you should be editing the version of CDT for that release which is CDT 8.8 located on the cdt_8_8 branch. For that version you should be using the cdt_e4.5.target.
>
> I am not 100% sure why there are multiple cdt_e*.target files on each branch as only one of them is ever technically correct. Perhaps to allow easy checking to see if a new CDT can be installed on an old Eclipse?
>

I'm not sure either. They don't work. I suggest we remove them. Any objections?

> Does that resolve your question?
>
> Thanks
> Jonah
>
> ~~~
> Jonah Graham
> Kichwa Coders Ltd.
> www.kichwacoders.com
>
> On 29 December 2015 at 04:49, Justin You <justin.you@xxxxxxxxxxxx> wrote:
>>
>> Hi All:
>>
>>  
>>
>> Thanks, It works.
>>
>>  
>>
>> But 4.5.1 is the latest stable release version and I don’t understand why we have to target to 4.6. I suppose that master should works on 4.5.1 when target on cdt_e4.5. am I wrong? Thanks in advance.
>>
>>  
>>
>> -Justin
>>
>>  
>>
>>  
>>
>> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sergey Prigogin
>> Sent: 2015年12月16日 9:12
>> To: CDT General developers list.
>> Subject: Re: [cdt-dev] Compiler errors in latest master
>>
>>  
>>
>> Here is the procedure I used to get rid of these errors. Suggestions for a simpler procedure are welcome.
>>
>>  
>>
>> 1. Select cdt_e4.6 target platform acl click Edit
>>
>> 2. Select Eclipse SDK under 4.6milestones, click Reload
>>
>> 3. Click Finish
>>
>> 4. Check the check box next to cdt_e4.5, click Apply
>>
>> 5. Check the check box next to cdt_e4.6, click OK
>>
>>  
>>
>> -sergey
>>
>>  
>>
>>  
>>
>> On Tue, Dec 15, 2015 at 4:38 PM, Nathan Ridge <zeratul976@xxxxxxxxxxx> wrote:
>>
>> I'm seeing some compiler errors in latest master.
>>
>> Seems to have been introduced by the following commit:
>>
>> =======================
>> commit 8a834d59702025a3d1f44f379977b80068189213
>> Author: Alexander Kurtakov <akurtako@xxxxxxxxxx>
>> Date:   Mon Dec 14 11:06:00 2015 +0200
>>
>>     Cleanups.
>>    
>>     Remove useless:
>>     * casts.
>>     * suppress warnings unchecked.
>>     * @see comments
>>    
>>     Change-Id: I4713e9ddf90195cf1e465b3743f5f0bc7e41d338
>>     Signed-off-by: Alexander Kurtakov <akurtako@xxxxxxxxxx>
>> =======================
>>
>> For example, CSourceViewer.java line 188: Type mismatch: cannot convert from Object to String[]
>>
>> The line is:
>>
>>             String[] defaultIndentPrefixes= fIndentChars.get(IDocument.DEFAULT_CONTENT_TYPE);
>>
>> As far as I can tell, fIndentChars has type Map, whose get() function returns Object.
>>
>> Is there something I'm missing?
>>
>> Thanks,
>> Nate
>>
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://dev.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://dev.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://dev.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://dev.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://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top