11.07.2015 Views

CrossWorks for ARM User Guide

CrossWorks for ARM User Guide

CrossWorks for ARM User Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

•Click on the project item to remove from the Project Explorer tree view.•On the Project Explorer toolbar, click the Remove button (or type Delete).—or—•Right click on the the project item to remove from the Project Explorer tree view.•From the popup menu, click Remove.Project propertiesFor solutions, projects, folders and files - properties can be defined that are used by theproject system in the build process. These property values can be viewed and modifiedusing the properties window in conjunction with the project explorer. As you select anitem in the project explorer the properties window will list the set of properties that areapplicable.Some properties are only applicable to a given item type. For example linker propertiesare only applicable to a project that builds an executable file. However other propertiescan be applied either at the file, project or solution project node. For example acompiler property can be applied to the solution, project or individual file. By settingproperties at the solution level you enable all files of the solution to use this propertyvalue.Unique propertiesA unique property has one value. When a build is done the value of a unique propertyis the first one defined in the project hierarchy. For example the Treat Warnings AsErrors property could be set to Yes at the solution level which would then be applicableto every file in the solution that is compiled, assembled and linked. You can thenselectively define property values <strong>for</strong> other project items. For a example particularsource file may have warnings that you decide are allowable so you set the TreatWarnings As Errors to No <strong>for</strong> this particular file.Note that when the properties window displays a project property it will be shown inbold if it has been defined <strong>for</strong> unique properties. The inherited or default value will beshown if it hasnt been defined.solution — Treat Warnings As Errors = Yesproject1 — Treat Warnings As Errors = Yesfile1 — Treat Warnings As Errors = Yesfile2 — Treat Warnings As Errors = NoChapter 4Project properties49

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!