Hi,
Since we
have resource bandwidth available and are ready to help the work to progress on
the build, it is important to adopt an easy process to allow Sam to submit the
build code as soon as he can. If putting the code in the main stream is not a
longer process that the side branch, I will support having the code in the main
stream since it will help us to move forward quickly on getting the CDT product
available with build infrastructure. Since the build infrastructure is a
passive component in the CDT until you use it, this should not block the community
to use the CDT event if build is part of the main stream.
As for the
directories, I agree with Doug.
Regards,
Michel Paquet
Technical Software Product Engineering
Director,
Practitioner Desktop Group
Product responsibilities: Rose Real Time
& UML Automation
770 Palladium Driver
Kanata, Ontario
K2V 1C8
Tel: (613) 591-7943, Fax: (613) 591-7020
Email: mpaquet@xxxxxxxxxxxx
R a t i O n a l
the software
development company
-----Original
Message-----
From: Schaefer, Doug
[mailto:dschaefer@xxxxxxxxxxxx]
Sent: Thursday, February 13, 2003
3:35 PM
To: 'cdt-dev@xxxxxxxxxxx'
Subject: 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
Senior
Staff Software Engineer
Rational - the
software development company
Ottawa (Kanata), Ontario, Canada
-----Original
Message-----
From: Sebastien Marineau [mailto:sebastien@xxxxxxx]
Sent: Thursday, February 13, 2003
3:20 PM
To: 'cdt-dev@xxxxxxxxxxx'
Subject: RE: [cdt-dev] Build Model
Source Code
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
-----Original
Message-----
From: Evoy, Sean
[mailto:sevoy@xxxxxxxxxxxx]
Sent: Thursday, February 13, 2003
2:21 PM
To: CDT Developer List (E-mail)
Subject: [cdt-dev] Build Model
Source Code
Hi Sam,
Just wondering if we could get hold of your
source code? Doug Schaefer has commiter priveleges and I know he would be
willing to create a branch and patch onsite here if that would expedite things
for you. In any case, I am looking forward to working with you on advancing the
build model!
Sean
Evoy
Senior Software Engineer
Rational Software
mailto:sevoy@xxxxxxxxxxxx