From c4352070c0b47071bdaf2c8b88fe39a20b05e1ee Mon Sep 17 00:00:00 2001 From: Mikhail Sennikovsky Date: Fri, 22 Jun 2007 19:25:00 +0000 Subject: [PATCH] Added a link to "what's new in CDT Build System doc" --- .../Managed_Build_Extensibility.html | 30 +++++++++++++++---- 1 file changed, 24 insertions(+), 6 deletions(-) diff --git a/doc/org.eclipse.cdt.doc.isv/guide/mbs/extensibilityGuide/Managed_Build_Extensibility.html b/doc/org.eclipse.cdt.doc.isv/guide/mbs/extensibilityGuide/Managed_Build_Extensibility.html index 511143d5954..d0045306997 100644 --- a/doc/org.eclipse.cdt.doc.isv/guide/mbs/extensibilityGuide/Managed_Build_Extensibility.html +++ b/doc/org.eclipse.cdt.doc.isv/guide/mbs/extensibilityGuide/Managed_Build_Extensibility.html @@ -93,7 +93,7 @@ managed build system and how to extend it. Chris Recoskie - Revision Date + Revision Date 10/21/2003 - Version: 0.1.0 @@ -112,7 +112,10 @@ managed build system and how to extend it. 05/09/06 - Version 3.1 - Change History + 06/22/07 - Version 4.0 + + + Change History 0.1.0 - Document Creation @@ -129,6 +132,11 @@ managed build system and how to extend it. 3.1 - Updated for CDT 3.1 + + + 4.0 Added link to + "what's + new in 4.0" document
@@ -211,6 +219,15 @@ managed build system and how to extend it.

1 Introduction

+

NOTE: +the document describes the CDT Managed Build System (MBS) 3.x functionality. +Although there have been lots of significant changes made to the Build System in +the 4.0, the document still remains valid since all the 4.0 build system changes +were made by extending the MBS functionality described in this document.

+

Please refer to the +"What's new +in the CDT Build System 4.0" document for the list and description of +additional new functionality presented in CDT 4.0

C and C++ developers are a diverse group. The tools they use, the processes they follow, and the level of support they expect from their development environments vary widely. The CDT provides a framework for @@ -253,10 +270,11 @@ needs, then you do not need to modify anything. Please feel free to skip sections 3, 6, 7 and 8, as they are primarily concerned with adding new tool integrations to the build model.

If you are working with tools other than GCC, or you wish to create -project-types that CDT does not support out of the box, then you have to -decide whether you will provide your own makefile and use the standard builder, -or add a description of your project-type to the extension point and -let the CDT generate the makefiles for your project.

+project-types that CDT does not support out of the box, you can add a +description of your project-type/toolchain and make the CDT pick up the +information you provide with your definitions. With the CDT 4.0 you can do this +for both cases whether you are willing the CDT to automatically generate +makefiles for your project or not.

If you choose to add your own tools to the managed build system, it is assumed that you are familiar with XML and the Eclipse extension point mechanism. Having made the standard disclaimer, it should be said