|
» Subscribe » Favorite Links » What is S60? » Freeware & Trials » S60 devices » Hints and tips » About this blog |
» Blognotes (15) » Bugs and Workarounds (4) » Build tools (5) » Carbide.c++ 1.1 (4) » Carbide.c++ 1.2 (8) » Carbide.c++ 1.3.x (9) » Carbide.c++ 2.0.x (12) » Carbide Plug-Ins (4) » CodeWarrior (2) » FAQ (6) » Future directions (25) » General (48) » Off-topic (5) » On-device debugging (13) » Performance Investigator (2) » Product features (18) » Product releases (16) » Screencast (14) » Support (36) » Tool setup (6) » UI Designer (8) » Usability (18) » Work in Progress (14) » Write-build-debug (4) |
|
» New Remote Connections View » Terminating Multiple Processes » Agile Tuning of the Austin Team » Introduction to the workspace screencast » Adding DLLs while Debugging |
|
Subscribe to RSS feed For email notification, please click here ยป |
« C++ Refactoring in CDT | Main | Forgotten, but not Gone »
For this quick tip I thought it might be helpful to point out where customers can set their own build options in Carbide that take place after our build process. This can be useful for things like running a batch file after the build, but customers haven't always known where to find the option for this. In Carbide.c++ v1.3, with the project highlighted choose the "Project" and "Properties" option from the menu bar.
Once in the project settings, click on the "Builders" option and select New. This will bring up the Configuration type window box. From there choose the "Program" option and select OK. This will bring up the launch configurations properties box: ![]()
There you have it, now you can add a builder to projects that will run after our builder.