ArcGIS Engine Developer Guide

BUILDING A COMMAND-LINE C++ APPLICATION
The C++ API section of Chapter 4, ‘Developer
environments’, has a detailed discussion of error
checking. You are encouraged to read it for more
information.
If you are unfamiliar with the nmake utility, see
the Microsoft Developer Network for further
information.
A template copy of Makefile.Windows, like the
one provided in this scenario's solution code, is
included in the ArcGIS Engine Developer Kit and
can be accessed from the help system under
Development Environments > C++ > Makefiles
as Makefile.Windows.
Replacing all instances of basic_sample in your
Makefile.Windows file with RasterSlope will
complete steps 3 and 5 through 7 listed at
right.
IMPLEMENTATION
The implementation below provides you with all the code you will need to
successfully complete the scenario. It does not provide step-by-step instructions
to compile C++ applications, as it assumes that you already have a working
knowledge of your chosen development environment. Error checking has been
left out to increase code readability.
This scenario’s sample application demonstrates ArcGIS Engine Spatial extension
functionality; the full source code is available in the samples included in the
ArcGIS Engine Developer Kit. Here are the files discussed in this scenario:
• RasterSlope.cpp—Main C++ source file.
• RasterSlope.h—Main C++ header file.
• Makefile.Windows.template—nmake utility file template. During this exercise,
you will copy this file from the solution code and rename it
Makefile.Windows. You will then update it while following the scenario.
• Makefile.Windows—nmake utility file that specifies compiler settings and
rules, file dependencies, input arguments, and an execution rule for our application.
In the solution code, this file is the completed makefile for the scenario.
As you work through the scenario, the name will refer to the makefile
you are building.
• PathUtilities.cpp—Platform-independent path processing helper function
implementation file.
• PathUtilities.h—Platform-independent path processing helper function header
file.
The following files are provided for your use if you choose another compilation
option: Makefile.Solaris and Makefile.Solaris.Template, Makefile.Linux and
Makefile.Linux.Template, vs6.dsp and vs6.dsw, and vs7.sln and vs7.vcproj.
Creating your build environment
This scenario uses nmake to build and deploy its application. To utilize nmake,
you must write a makefile for it to execute. This scenario is not designed to teach
you the basics of project management with the nmake utility. However, this
scenario will step you through the parts of the makefile that must be customized
for each application you build.
First, copy Makefile.Windows.template from this scenario’s solution code to your
coding directory. Once you have the file copied to your coding directory, follow
the steps outlined below to prepare it for use:
1. Rename your copy of Makefile.Windows.template to ‘Makefile.Windows’.
2. Open the newly renamed Makefile.Windows.
3. Update PROGRAM to be RasterSlope.exe.
4. Update INCLUDEDIRS macro, which contains the include directories to pass
to the compiler, to reflect where you installed ArcGIS Engine.
5. Update CPPSOURCES to be RasterSlope.cpp.
6. Update CPPOBJECTS to be RasterSlope.obj.
Chapter 6 • Developer scenarios • 429