## Workspace Information

A workspace is the default place to store and create resources like projects, folders, and files. These are then presented to the user in a perspective which enables the presentation and manipulation of the stored resources.

When Carbide is launched it asks for a workspace to open (Figure 1). As you can have multiple workspaces, all independent from each other, choosing the workspace containing the projects to work on is important. Projects within a workspace are shown in the Carbide workbench within the Project Explorer and C/C++ Project views. When you create a new project it is automatically added to the currently open workspace. You can import existing projects into a workspace from INF files.

Figure 1. Workspace Launcher dialog

WARNING Bld.inf imported projects are not copied, so do not delete the contents when deleting the project.

Projects in one workspace cannot refer to projects in a different workspace. Thus, large projects spanning folders outside of the workspace are not handled at all. Storing all the project files in the workspace makes managing them easier from a project management perspective. Files accessible inside the workspace, like project source and resource files, are better supported than those outside the workspace (for example, SDK headers). Local History, CVS, MMP/bld.inf editors, etc. are available for files inside the workspace but not for those outside the workspace.

NOTE Carbide automatically updates MMP and INF files as changes are made within the MMP and INF editors.

Carbide generates project support files, such as .project and .cproject and a .metadata folder, which stores preferences. Metadata files like ".project" are placed in the source tree. If adding these files to CVS causes a problem, these files may be excluded from CVS using Team > Ignored Resources preference panel to specify name patterns to exclude from version control.

#### Other references

- Carbide.c++ perspective
- Debug perspective