| RE: [cdt-dev] Build Model Source Code |
|
I don't mind putting it in the head. I would think we need to maintain the standard make project(s) and introduce this as a new project type. In the immediate term, to help us get started, it should go in dormant and not get activiated until the new project type (or whatever other mechanism we choose) is set up.
As for directories, it would probably be nice if we had a source folder for each major component of a plugin. As such we could create a 'build' folder in each of cdt.core and cdt.ui to hold this.
I'd like to see other opinions on this, though?
Cheers, Doug Schaefer Rational - the software development
company -----Original Message-----
Actually, I was going to comment on Doug's proposal to create a branch. Since we are aiming to get a prototype of the build model out for March/April, I think we should just put it in the head (provided it builds), and have some toggle to use the old builder or the new build model. Having it on the head will make it more visible and accelerate the build model's evolution.
Also, could we discuss where it would fit (directory/etc) in the cdt.core/cdt.ui?
Thanks,
Sebastien
|