At this point, if you add C and C++ source files to your project and build your project (CTRL + B), your files should be automatically be processed into a PDF file - assuming your system is set up with make, enscript, and ps2pdf in your path. By using the C/C++ Project view or the Eclipse Navigator view to browse the automatically generated "Default" folder (named after the "Default" configuration you created in your tool-chain), you should be able to see the resulting PDF file (see Figure 3).
If you're using Windows as your OS, you should even be able to open the PDF file directly if you have a PDF viewer installed that is associated with the .pdf file extension (see Figure 4 for the resulting PDF file viewed in Adobe Acrobat Reader).
Now select your project and display its properties. If you select the C/C++ Build item in the left pane, you can set the options that you have defined for the PostScript PrettyPrinter tool. Select the General category and you will see two check boxes for the options that you defined (see Figure 5). Try unselecting one or both of the options and see how the enscript command line is affected by selecting the PostScript PrettyPrinter tool and examining the All options field.
That completes our sample tool-chain definition. For more information on how to create extensions to the MBS, see the CDT Plug-in Developer Guide, Programmer's Guide, Managed Build System Extensibility Document, which is provided with the CDT SDK.
Chris was, at the time this article was written, a senior software designer with Texas Instruments Canada Limited and is a CDT Committer. He can be reached at firstname.lastname@example.org. Leo is the IDE architect in the Intel Compiler Lab at Intel Corporation. He can be contacted at email@example.com.