[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cdt-dev] Two more suggestions for CDT 2.0 Managed Build functionality
- From: Douglas Schaefer <dschaefe@xxxxxxxxxx>
- Date: Fri, 31 Oct 2003 08:43:48 -0500
- Delivered-to: firstname.lastname@example.org
Thanks, Leo, this is great feedback.
I am currently gathering all the info and will produce a proposal by the
end of next week. We can then have a thorough discussion at the Nov 12
meeting and hopefully come up with some good plans to get started on.
Doug Schaefer, Senior Software Developer
IBM Rational Software, Ottawa, Ontario, Canada
"Treggiari, Leo" <leo.treggiari@xxxxxxxxx>
Sent by: cdt-dev-admin@xxxxxxxxxxx
10/30/2003 07:04 PM
Please respond to
[cdt-dev] Two more suggestions for CDT 2.0 Managed Build functoionality
These suggestions come from the folks working on the compilers for
embedded systems for your consideration:
1. When a user creates a managed make project, at some point they
may want to turn off make file generation and maintain the
make file themselves. For instance, to add functionality that
cannot be added via the managed make UI. I had 2 thoughts on
how to provide this:
o Provide a Managed Make project to Standard Make project
converter that used the last generated make file as the
make file for the Standard project.
o Provide a "switch" in the managed make UI that turns off
make file generation. When the switch is set, a build
would not re-generate the make file, merely invoke it.
2. One of Intel's IDEs supporting embedded systems implements a
build system that is flexible in terms of adding new tools to
the build system. A concept that they use in the build system
is that of a "process" (or step). In other words, a tool chain
consists of a series of processes and each process invokes one
of more tools. Processes are abstract steps such as "Compiling"
and "Linking". If the user needs to add a new tool to their
build system, they add the tool to the appropriate process.
cdt-dev mailing list