EETimes

Embedded Systems September 2000 Vol13_10

Issue link: http://dc.ee.ubm-us.com/i/71837

Contents of this Issue

Navigation

Page 175 of 229

All in all, the build boss is responsible for the smooth operation of the SCM system. His value cannot be understated and every development team should have one. he decides if it is warranted. All in all , the build boss is responsible for the smooth operation of the SCM system. His value cannot be understated and every development team should have one. A change package is a logical grouping of all the fi les that were modified through th e course of some unit of development work (for example, PRCR). Rarely does any but the most trivial bug fix requi re modificatio n of only one fi le. Rather, the bug fix spans multiple files that are in ter-dependen t to get a working execu table. Trying to build with th ree of the fou r files that were changed will likely not even compile. Since using the modified versions of the affected files is an aU- or-nothin g propositio n , it makes sense to track them as a single unit of change. This creates the capabili- ty to undo the entire change should a problem or question concerning th e PRCR ever arise. This concep t is directly supported by such SCM too ls as Con tinuus/ CM, Clear- Guide, and others. Of course it can be manually supported by any SCM user through such mechanisms as release notes (discussed next ). A release is a formalized build that Our inspiration. Powerful tools. Great productivity. Integrated price. Paradigm introduces all the tools you'll need for x86 integration in one package. Paradigm C++ is alone in offering a complete integrated development environment that includes all the tools you need to get your x86 embedded application jump started. Editing, project management, debugging, compiler, assembler, version control and more, all fu lly integrated into the powerful Paradigm C++ development environment. If you are tired of wasting time on non-integrated tools, then Paradigm C++ is where you want to be. Download a copy of Paradigm C++ from http:/ fwww.devtools.comfpcpp and see the future of x86 development tools today. Paradigm Paradigm Systems 3301 Country Club Road Suite 2214 Endwell, NY 13760 1-800-537-5043 Phone 607-748-5966 Fax 607-748-5968 info@devtools.com http:ffwww.devtools.com creates a milestone product. The product itself can be for internal consumption only, or for delivery to a customer. Typically a re lease involves applying a label to all ver- sioned fi les. The label provides a means for getting a specific version of a fi le by name rather than num- ber. This is a convenience for devel- opers by logically grouping specific versions of all the fil es that create a build. The manual alternative would be to keep a list of the version num- ber for every fi le needed to build a given execu table. The release notes are a simple ledger created after a version label is applied to the source code. It lists all the fil es that were modified, the ver- sion used in the previous release, the version used in the current release, the order in which branches were merged into the mainline, and a brief description of the reason for the change, or a reference to the PRCR that the work was performed against. 174 SEPTEMBER 2000 Embedded Systems Programming

Articles in this issue

Archives of this issue

view archives of EETimes - Embedded Systems September 2000 Vol13_10