[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] F1 CDT works under Linux but not Windows
|
Some things I've never understood in terms of the process of
development:
1. Why is the cdt is in a separate CVS archive instead of just being a
separate CVS module in the same archive? In fact, with all the Eclipse
plug-ins popping up on SourceForge and elsewhere, it would seem that it
would make much more sense to encourage these developers to work out of
an eclipse.org repository in the name of building a community. Of course
if we can't integrate the cdt stuff, I guess it would be silly to expect
some random plugin to have a project there...
2. The CDT build process (though somewhat obscure, much better
documented now thanks to Jeff!) at least has a fairly simple "make" kind
of interface. Of course all the other components have their own make
processes. This is fine, but there should be documentation for each
process, and it would help if there was a single top level build process
that could bootstrap the whole shebang... So wouldn't it be more
efficient to spend a little time cleaning that up in an effort to
simplify the process for everyone?
3. While I understand it's good to compartmentailize some development
such that the cdt stuff is being developed with the 'last known good'
core eclipse stuff, it would also be good to be building it with the
current stuff so there is a shorter feedback loop to concurrent
versioning. Has anyone looked at that?
4. The core eclipse CVS has a vast quantity of tag information. This is
actually pretty useful in terms of trying to determine where stuff
changed and which changes went together. Has anybody looked into a
policy for tagging more like what the eclipse core is doing?
Anyway, there's my questions/opinions... They're free and probably worth
at least that much :). Thanks for listening.
--
Joe
On Thu, 2002-05-30 at 07:22, turnham@xxxxxxxxxx wrote:
> Hi Brian and All,
>
> I've created a document that describes the steps to build/run/debug the CDT
> inside Eclipse (as well as how to build the CDT from the command line).
> The document is here ->
> http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/cdt-home/developer/build/developingCDT.html?cvsroot=Tools_Project
> Please let me know if there are any problems with the document. I think
> I'll add some screenshots when I get some time.
>
> Just to clarify Brian...the CDT does not build Eclipse itself. It simply
> builds against the Stable builds available on http://download.eclipse.org.
>
> Hope that helps...
>
> Jeff.
>
>
>
>
> Brian Moyle
> <bmoyle@mvista. To: cdt-dev@xxxxxxxxxxx
> com> cc:
> Sent by: Subject: Re: [cdt-dev] F1 CDT works under Linux but not Windows
> cdt-dev-admin@e
> clipse.org
>
>
> 05/29/2002
> 06:50 PM
> Please respond
> to cdt-dev
>
>
>
>
>
> I forgot an important point when writing this email. There's something
> called "nightly" and "integration" builds on the eclipse web site. Is
> the formula as simple as "we use the latest integration builds?"
>
> I think I confused myself with a previous email and what was available
> on the web site at the time. I believed the CDT team was working with a
> version of Eclipse that I didn't have access to, but now that I think
> about it, I may have just been mistaken.
>
> Brian
>
> Brian Moyle wrote:
>
> > Thank you, Jeff!
> >
> > I may be getting somewhat off-topic here, so let me know if I should
> > move this discussion elsewhere.
> >
> > Does the CDT team receive pre-built versions of eclipse from the Eclipse
> > team? If not, does that mean there's a recipe for building Eclipse from
> > a CVS snapshot? I had initially intended to try to reproduce this
> > problem with the latest CVS trees (Eclipse and CDT), just in case it had
> > already been fixed. After stumbling around a bit, trying to figure out
> > which modules need to be checked out, which ones are built using Ant,
> > whether the CVS versions of Ant and Xerces are sufficient to build SWT,
> > how to build all of Eclipse (from either inside or outside of Eclipse
> > itself), etc., I finally decided there might be an easier way. I've
> > read a number of messages that lead me to believe the build support
> > is/was changing for Eclipse, and it could still be changing, but it's
> > not completely clear from what I've read. Does anybody have pointers or
> > suggestions on how to build/package Eclipse? Again, I think I'm most
> > interested in knowing how the CDT team deals with the problem.
> >
> > thanks,
> >
> > Brian
> >
> > turnham@xxxxxxxxxx wrote:
> >
> >> Hi Brian,
> >>
> >> I just reproduced the same problem...I opened bug 18129
> >> (http://bugs.eclipse.org/bugs/show_bug.cgi?id=18129). If you wish to be
> >> notified when this bug gets some attention, add yourself to the bug's cc
> >> list (you'll have to create a bugzilla account first ->
> >> http://bugs.eclipse.org/bugs/createaccount.cgi).
> >>
> >> Thanks for including all the relevant info!
> >>
> >> Jeff
> >
> >
> >
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
>
>
>
> --
> Member, Technical Staff Phone: (408) 328-8521
> MontaVista Software, Inc. Fax: (408) 328-3875
> 1237 East Arques Avenue Web: http://www.mvista.com
> Sunnyvale, CA 94085 Email: bmoyle@xxxxxxxxxx
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
