Writing MSP430 C Code
Build Configurations
Early in development, most users always use the Debug compiler options.
Later in the development cycle, it is common to switch back and forth between Debug and
Release (i.e. optimize) options. It is often important to optimize your code so that it can perform
your tasks most efficiently … and with the smallest code footprint.
Rather than forcing you to continuously tweak options by hand, you can use Build Configurations.
Think of these as ‘groups’ of options.
When you create a new project, CCS automatically creates two Build Configurations:
− Debug
− Release
This makes it easy for you to switch back and forth between these two sets of options.
Even further, you can modify each of these option sets … or create your own.
Hint: If you modify a Project build option, it only affects the active build configuration.
This is a common source of errors. For example, when you add a new library search path
to your project options during Debug, it only affects that configuration. This means that
it’s common to run into errors whenever you switch to the Release build configuration.
CCS is trying to help – and often asks if you want to update both/all configurations. But,
this is a new feature and only works for some of the options. This means that when an
option should apply to all configurations, you should (manually) change them both at the
same time … or be prepared to tweak the Release build options the first time you use it.
2 - 22 MSP430 Workshop - Programming C with CCS
To Next Page
Loading...
Need help?
General
