|
Hello Developer. How are you doing with your project?
This is another in our series of emails designed to
familiarize you with the many
features in TrueSTUDIO that can save you time and/or
improve your project.
In this installment we talk about another hidden gem:
build configuration options.
Embedded tools have improved a lot over the
years. Long gone are the days when developers had to use line
editors (if you are old enough you might remember EDLIN,
the only editor bundled with MS/DOS before v5.0 of the
operating system). In fact, most people don't even use standalone
visual editors these days; since the deeply integrated, modern IDEs
provide so much more value and efficiency.
However, there was one advantage with the
non-integrated tools embedded developers had to put up with decades
ago: makefiles.
While many consider makefiles to be ancient
dinosaurs or something from the dark ages, they did have one distinct
advantage over some of today's tools -- it was easy to build the
project in different ways, either by using the flexibility of the
makefile grammar itself, or by just copying the makefile and changing
it to get a different build recipe.
With makefiles, it was easy to create
predefined recipes on how the build was going to be made; either by
changing some compiler options, or even using a different set of
C/C++ source code files to create a more dramatically different
build. Luckily for you, it is still possible to achieve the power and
flexibility of makefiles while still enjoying the convenience of an
integrated, graphical point-and-click configuration tool.
In TrueSTUDIO this is done using the Build
Configurations option. We have put together a short tutorial as part
of a blog post to demonstrate how you can easily use build
configurations in your project:
The tutorial shows you how you can create a new
build configuration to generate a binary with different build
settings or with a different code base.
Stay tuned for more tips and tricks!
Sincerely,
The TrueSTUDIO product team
|
