[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] bug 219337 - CDT trigger re-build on non changed project dependencies
|
Yes, i agree on the option, but would prefer the new behavior to be
default. i.e no build is fired when eclipse resource has not been changed .
This is because, Bug 210349 was raised because CDT behavior effected other
tools that has no relation with CDT. Also external files effecting the
eclipse CDT project is an advanced use case.
- Janees
Re: [cdt-dev] bug 219337 - CDT trigger re-build on non changed project
dependencies
Elena Laskavaia
to:
CDT General developers list.
20/11/2008 01:02 PM
Sent by:
cdt-dev-bounces@xxxxxxxxxxx
Please respond to "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
I think we all agreed on option. And preserve current behavior as default
for this option.
Chris Recoskie wrote:
> Upon further thinking, I believe we're going to need the option, because
> if we go to the new way that has been proposed, then changes in external
> libraries will never trigger a build. The only way then to relink will
> be to do a clean, which could be time consuming. Thoughts?
>
> ===========================
>
> 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
>
> 11/19/2008 04:37 PM
> Please respond to
> "CDT General developers list."
<cdt-dev@xxxxxxxxxxx>
>
>
>
> To
>
> "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
>
> cc
>
>
> Subject
>
> Re: [cdt-dev] bug 219337 - CDT trigger re-build on non changed project
> dependencies
>
>
>
>
> I think we need a preference. Eclipse does not always knows what
> something is changed unless refresh is forces
> (i.e. people edit files with vi or use command line tool source manager)
>
> Vivian Kong wrote:
> > Currently when we build a CDT project, the external builder invokes
> > 'make all' on the project and all its dependencies and lets 'make'
> > figures out what needs to be build. We have a requirement to change
this
> > behaviour so that 'make' gets invoked only when the project and its
> > dependencies have changed within Eclipse. I've attached a patch on
> > bugzilla for this change.
> >
> > I'm wondering if anyone is relying on the current behaviour. If so, we
> > can always add a new option for the proposed change in CDT preference.
> >
> > Regards,
> >
> > Vivian Kong
> > IBM Eclipse CDT
> > IBM Canada Toronto Lab
> >
> >
> >
------------------------------------------------------------------------
> >
> > _______________________________________________
> > 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
