Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: patch for 234860, was Re: [cdt-dev] How to create a CDT Standard MakeProject

I tested the latest patch with our Intel integration and it seems o.k. to me.  My testing is on linux.

 

Not to distract from the immediate question, but it would also be nice if there were a way to filter the C++ projects out of the offerings when creating a C project thru “New C Project” wizard.  In cdt4.0, if the user chose the C++ project example, they got the “nothing to build” message.  I just noticed in cdt5.0, they will get that message plus a nice big marker in the editor view for “unresolved inclusion” on “#include <iostream>” in the source.

 

Thanks,

 

Bill

 


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Chris Recoskie
Sent: Monday, June 02, 2008 9:58 AM
To: CDT General developers list.
Subject: patch for 234860, was Re: [cdt-dev] How to create a CDT Standard MakeProject

 

Everyone,

I have looked at this patch and am of the opinion we should commit it. Please take a look and see if you object. I am awaiting a more refined patch from the submitter before I think about committing it, but if no one objects to the basic idea of the patch I will commit it sometime in the next couple of days (but not before tomorrow morning Eastern time in order to give everyone a chance to object).

https://bugs.eclipse.org/bugs/show_bug.cgi?id=234860

===========================

Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt

Inactive hide details for Chris Recoskie/Toronto/IBM@IBMCAChris Recoskie/Toronto/IBM@IBMCA

Chris Recoskie/Toronto/IBM@IBMCA
Sent by: cdt-dev-bounces@xxxxxxxxxxx

05/30/2008 01:18 PM

Please respond to
"CDT General developers list." <cdt-dev@xxxxxxxxxxx>

To


"CDT General developers list." <cdt-dev@xxxxxxxxxxx>

cc

Subject


Re: [cdt-dev] How to create a CDT Standard Make Project

 


I would like the chance to look at the patch before we decide. I'll start this during the afternoon. I'll let you know what I think. We're in the home stretch now so we have to be extra careful about whatever we put in up until GA.

Thanks,

===========================

Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt

Inactive hide details for Elena Laskavaia <ELaskavaia@xxxxxxx>Elena Laskavaia <ELaskavaia@xxxxxxx>

Elena Laskavaia <ELaskavaia@xxxxxxx>
Sent by: cdt-dev-bounces@xxxxxxxxxxx

05/30/2008 01:00 PM

Please respond to
"CDT General developers list." <cdt-dev@xxxxxxxxxxx>

To


"CDT General developers list." <cdt-dev@xxxxxxxxxxx>

cc

Subject


Re: [cdt-dev] How to create a CDT Standard Make Project

 


I can look at this but we had a feature freeze and I though we cannot do
such changes now.
If everybody thinks it is ok to change in 5.0 I can apply the patch.

Schaefer, Doug wrote:
> As per my previous message. I'm not counting on build patches getting
> applied anytime soon until we get new blood working on the build system.
>
> Doug.
>
>  
>> -----Original Message-----
>> From: cdt-dev-bounces@xxxxxxxxxxx
>> [
mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Vladimir Prus
>> Sent: Friday, May 30, 2008 11:15 AM
>> To: CDT General developers list.
>> Subject: Re: [cdt-dev] How to create a CDT Standard Make Project
>>
>> On Friday 30 May 2008 18:37:10 Oberhuber, Martin wrote:
>>    
>>> Dear all,
>>>  
>>> Thanks for the very positive responses to this message.
>>>  
>>> I didn't find a proper existing bug in bugzilla, so I filed
>>>
https://bugs.eclipse.org/bugs/show_bug.cgi?id=234860
>>>  
>>> Vladimir, attaching your patch on that bug would be highly
>>> appreciated. I encourage all interested parties to CC on the bug.
>>>      
>> Done.
>>
>> On Friday 30 May 2008 18:50:52 Schaefer, Doug wrote:
>>    
>>> The easiest solution would be to create an Empty template
>>>      
>> for each of
>>    
>>> the project types that don't have one. Creating templates is
>>> documented in CDT's ISV docs. Or you can follow the examples of the
>>> ones that are already there.
>>>      
>> Why is this better, given that the code patch already exists?
>>
>> - Volodya
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>>
https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>
>>    
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/cdt-dev
>  
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top