RE: [cdt-dev] Build Model Enhancements for CDT 8.0

["Treggiari, Leo" <leo.treggiari@xxxxxxxxx>]

> I do not plan on using the managed build model for the other "managed
> build systems". They usually have their own system for specifying
> tools and options, such as CMake's CMakeLists.txt file, and qmake's
> .pro project files. It probably make more sense to have good editors
> for those files than manage these settings in the properties pages.

For the current MBS, the property pages provide a simpler UI for specifying
the information necessary to create the make file (or for the internal
builder).  Wouldn't you want to allow the same capability for other
managed builders - i.e. the ability to provide property pages as an
alternative to directly editing the "project files".  For example, in 
Qt Creator, the .pro file can be managed from the UI - if I remember
correctly.  Ideally, you would provide a UI for specifying the
project/build information that does not require a user to understand the
project file format, plus the ability to edit the project file directly 
and automatically keep them "in-sync".

Leo

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Saturday, July 31, 2010 7:54 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Build Model Enhancements for CDT 8.0

On Sat, Jul 31, 2010 at 10:30 PM, Austin Morgan
<admorgan@xxxxxxxxxxxxxxxxxxx> wrote:
> On Sat, Jul 31, 2010 at 10:15:04PM -0400, Doug Schaefer wrote:
>> Hey gang,
>>
>> I've started an enhancement request for changes I'd like to make to
>> the Build Model, not the managed build model, but the build stuff in
>> the project model. My objective is to be able to enable other
>> "managed" build systems to be first class citizens in the CDT's build
> <snip...>
>
> In reading the documentation of CDT I was under the impression that the
> managed build model was superseding the Build Model.  If not can
> someone point me to the documentation?  I think it might help me with a
> project I am currently working on.

Well, it's a complicated subject. In the beginning we had the Managed
Build Model, things like IConfiguration, ITool, IOption and friends.
We often just shortened it to Build Model when discussing it in the
early days but at the end of the day, my claim is that this model is
really specific to managed build.

A couple of years ago we attempted to bring some of those concepts
into the CDT core and that is what is called the Project model, which
is not to be confused with the CModel which is what you see in the
Outline view. I hate the name Project model since outside of Build,
I'm not sure what it's used for.

So what I mention here is really updating the Project/Build model. The
Managed Build model extends the Project/Build model somehow which I
still find mysterious. But the managed build model is used by CDT's
managed build system which includes an internal builder and a makefile
generator that use this model.

I do not plan on using the managed build model for the other "managed
build systems". They usually have their own system for specifying
tools and options, such as CMake's CMakeLists.txt file, and qmake's
.pro project files. It probably make more sense to have good editors
for those files than manage these settings in the properties pages.

Doug.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev