Assignment 2
Methods In Medical Image Analysis (16-725 : BioE 2630) - Spring 2018

Creative Commons License ITK Development Environment Setup Assignment by John Galeotti (among others) 2012-2017 Carnegie Mellon University, is licensed under a Creative Commons Attribution 3.0 Unported License. Permissions beyond the scope of this license may be available by sending email to itk This assignment was made possible in part by NIH NLM contract# HHSN276201000580P.

20 points total

Due Date: Email your submission to the TA by 5 pm on Wednesday night, Feb. 7. Big problems may not show up until the end, so finish early!

Acknowledgement: This assignment is based on the work of others from previous sessions of this class.

E-mail the TA and instructor with questions or problems.

Before doing any ITK development later in the course, you will need to setup a working environment in which to compile and run your code. This includes

  1. Installing Support Programs: CMake, ITK-SNAP, and ImageJ
  2. Installing & Testing Python and SimpleITK for Python
  3. Compiling & Testing C++ VTK
  4. Compiling C++ ITK & C++ SimpleITK
  5. Testing C++ ITK

For further guidance on these procedures and how to test your build environment, you may wish to consult the slides from Lecture 4.

Note: Your life will be easiest if you use Mac OS X or Windows 7/8/10 for this class, or possibly RHEL/CentOS v7. But, we will try to work with you on other platforms as well.

WARNING: You may need up to 20 GB of free space for this assignment. If you are short on local disk space, then one possibility is to mount your BOX online storage space and compile SimpleITK into it. Both CMU and Pitt students have access to at least 1 TB of personal space on Box. On Windows or Mac you can use the official (but beta) Box Drive app. On Windows, Mac, and Linux you can alternatively directly connect to (mount) the Box WebDav Server as a local network drive (tutorial). When using Box this way, be sure to have the fastest internet connection you can while compiling VTK and SimpleITK (I suggest using a cable to direclty connect to the campus network). If space is still a problem for you, please send the instructor & TA an email.

Submission checklist: 

1. Screenshot from Step-2(a). Save the screenshot as 'Step2-Notebook.jpg'. 

2. Screenshot from Step-2(b). Save the screenshot as 'Step2-SITK.jpg'. 

3. Screenshot from Step-3. Save the screenshot as 'Step3-VTK.jpg'.

4. Screenshot from Step-4. Save the screenshot as 'Step4-SITK-Libs.jpg'. 

5. Screenshot from Step-5. Save the screenshot as 'Step5-TestITK.jpg'. 

Instructions: Please submit a single email to your TA and CC your instructor:

  1. The subject should be "HW2 Submission: " followed by your university ID, e.g. jgaleott or jmg113.
  2. The beginning of the email should list the assignment (HW2-ITK Install), your full name, and your university ID.
  3. If you have any special instructions or other write-up, please include that text next in your email.
  4. Please attach the required screenshots last. Please do not zip them; each screenshot should be attached separately. Be sure to attach them in the order of the steps, so the TA/instructor can quickly scroll through your email to check everything off.

0. Directory Structure (0 points)

Before you begin, create a new directory for this class, such as C:\MIMIA\ in a Windows environment or such as ~/MIMIA/ under Linux or OS X (Linux and Mac both recognize ~ as a shortcut for your home directory). You will probably find it convenient to keep all of your downloaded libraries (i.e., ITK, VTK, etc.) in this same MIMIA directory.

WARNING: If your username on your computer is longer than 8 characters, then do NOT put your MIMIA directory inside your standard "Documents" folder. Instead, you are strongly encouraged to put your MIMIA directory either in the top (root) folder of your hard drive (c:\MIMIA on Windows), or else in the top of your user's home directory (i.e., the folder that contains your Documents folder, e.g. c:\Users\{your user name}\MIMIA).

WARNING: Do not include any special characters (such as - $ @ : ; / \ [ ] ( ) { }) in the directory path to your MIMIA folder. For example, do not do something like "Documents/16725 - Med Image Analysis/MIMIA". Such special characters can easily interfere with shell scripts such as those used by CMake.

For the rest of this class, C:\MIMIA\ should be taken to mean whichever directory you created in this step, e.g. if you use a Mac, then when assignments say C:\MIMIA\ then you should presumably use either ~/MIMIA/ or ~/Documents/MIMIA/ instead.

Now, also create a directory for iPython Notebooks, such as C:\MIMIA\Notebooks\.

1. Installing Support Programs (0 points)


You should be able to do this assignment on Windows, Mac, or Linux/UNIX. If for some reason you do not want to install software into your normal environment (most users can skip the rest of this paragraph), then one option is to create a virtual machine for this assignment. Both VMWare and Parallels are fast virtual machines from commercial providers, but may be available to you under a campus or departmental license. VirtualBox is a free, open source virtual machine that can also be used, but your code may compile and/or run slower inside of a VirtualBox virtual machine. SimpleITK has a nice tutorial on setup up an appropriate enviroment in Linux, including steps to create a VirtualBox virtual machine and to install Ubuntu Linux on it. You can find the tutorial here, but only follow the first steps of installing Linux and build tools (the rest of the tutorial's instructions should be ignored and this assignment used instead). Also, after installing the build tools, be sure to install OpenGL developer libraries so that you can compile VTK too. Do this by using Ubuntu's command line to enter the command: sudo apt-get install freeglut3-dev


On Windows, if you do not already have Visual Studio 2010, 2012, or 2015 installed, you will probably want to do so now. (I now recommend 2015.) Beware that in the past CMake would get confused if you had VS 2015 installed in addition to previous version(s) of Visual Studio. CMU students should download Visual Studio 2012 or 2015 from CMU's Dreamspark Premium site (see the login button in the top-right corner, and when you choose visual studeio be sure to scroll down to get Professional or Enterprise, not Community Edition), and Pitt students should be able to get physical installation media from Pitt's campus. Otherwise, If you are a student, you can probably download Visual Studio 2015 Professional/Enterprise for free (after being certified as a student) from Microsoft's DreamSpark student program (alternate link). If asked for your preferred development settings/environment, I recommend choosing "Visual C++". In all cases, be sure to choose a custom install and choise to install the C++ components. After Visual Studio is installed, install all available online updates, especially the service packs, e.g. sp1 (Windows update should be able to do this for you, but you can also download Visual Studio service packs directly from Microsoft at Note that service packs can take several hours to install.

Visual Studio 2015 C++ Important Note #1: By default, Visual Studio no longer installs the C++ compiler. This is why we suggest you do a custom installation above. Alternateivly, if you already have Visual Studio 2015 installed, you can tell it to add the C++ tools by running Visual Studio and then clicking on "File" -> "New" -> "Project" -> "C++", after which you will be prompted to install the necessary C++ components if they are not already installed.
Visual Studio 2015 C++ Important Note #2: Visual Studio 2015 also requires Microsoft's C Runtime Library (CRT). This used to be included in Visual Studio, but is now included instead with Windows 10 (details here). If you are using VS 2015 on Windows 7 or 8 (or earlier), then you will need to install the CRT manually by installing the Visual C++ Redistributable Package for VS 2015.

Warning: Visual Studeio 2015 Community Edition sometimes messes up its own instalation, but can be fixed.

Warning: Visual Studio 2013 ("VS12") has (had?) an optimization bug that breaks several parts of ITK, and as of 2016 the bug was still present in the most recent 2013 updates. I do not know if the less-capable Express version of VS 2013 has this bug or not.

On OS X, if you do not already have XCode installed, you should do so now by downloading the latest version for free from Apple's App Store.

On Linux you hopefully already have gcc installed.


CMake can be downloaded from on the Download page (top-right menu option). The most recent binary distribution is 3.10.2. Use the binary distribution appropriate for your operating system.

On OS X, you will download a .dmg disk image. Open the .dmg file (if it doesn't open automatically), and then drag to the provided link to your Applications folder. Now open your applications folder, and then inside your Applications folder you must right-click on, and choose open from this menu. OS X will complain that is from an unidentified developer, and you then need to click the Open button. Fortunately, you only have to do this once; hereafter you can open CMake normally.

Installing CMake is relatively painless and you probably won't run into any problems here. I do, however, recommend letting the Windows installer add CMake to your system path (or, equivalently, letting the Mac installer "Install Command Line Tools").

Note: When using newer versions of CMake with pre-existing software, feel free to ignore any warnings about either "cmake_minimum_required" or "Policy CMP0003".


ITK-SNAP is a 3D medical image segmentation/viewer program, which internally uses ITK+VTK+Qt. It can be downloaded from on the Downloads page. I suggest getting that latest version, currently 3.6.0. Use the binary distribution appropriate for your operating system. Installing ITK-SNAP is relatively painless and you probably won't run into any problems here. (Don't worry about any so-called errors you may get stating "A newer version of Microsoft Visual C++ 2010 Redistributable has been detected on the machine." ITK-SNAP will still work fine.)

Fiji / ImageJ

ImageJ is a Java-based image processing/analysis/viewer program, which is called by SimpleITK's "show" command as a simple means to quickly view images. ImageJ can be downloaded as part of Fiji from Download the version of Fiji appropriate for your operating system. Windows users should unzip Fiji into their MIMIA diretory, where a folder will be created. Installing Fiji/ImageJ is relatively painless and you probably won't run into any problems here.

On OS X You may need to open Fiji "normally" once, using the icon in your Applications folder once, so that Fiji can configure itself and/or get permission to run from OS X. After that, then SimpleITK should be able to launch Fiji using the Show command.

2. Installing Python and SimpleITK for Python (5 points)

Python is an interactive python shell. By interactive, I mean python executes each line as you enter it, similar to Matlab. It makes rapid prototyping with SimpleITK very easy.

New for 2015: SimpleITK is now prepackaged for the Anaconda distribution of Python, drastically simplifying cross-platform SimpleITK python installation. More information is available about Anaconda, including help and tutorials.

If you do not yet have 64-bit Anaconda installed

Download the latest Anaconda version for Python 3.6 from 64-bit is recommend (Assuming you have a modern 64-bit operating system). (Warning, Google Chrome on Windows may have issues downloading this file, so I recommend using a different browser for this download.)

Install the verion of Anaconda you just downloaded. Don't worry about warnings about being from an unknown publisher. When prompted, select to install for "Just Me" (in your home directory\anaconda). If asked, select to "Add Anaconda to my PATH...". I do NOT recommend making Anaconda your "default" Python (unless you're using Windows and you also know that neither your nor anyone else has installed another version of Python before).

Now open a command line window:

To open a command-line window (i.e., a command prompt)
On Windows one way to open a command-line window (i.e., a command prompt) is to click on the start menu, which will show either a search box or a Run... command. Using either of these, enter the text cmd then hit enter. You can do this really quickly without using a mouse by just pressing the "Windows" key and then typing cmd and hitting enter.

On OS X You can simply run the Terminal program located in your Applicaitons/Utilities folder. (Or, even better, you can install and use the free iTerm2 program.)

On Linux you hopefully already know how to open a command prompt (oftern called a Terminal or a Bash shell, etc.).

On Windows, once you have the command line open, you may need to enter a command to tell SimpleITK where to find your ImageJ viewer inside of your folder (edit the following path to be where ImageJ is installed on your computer):

setx SITK_SHOW_COMMAND "c:\MIMIA\\ImageJ-win64.exe"

(If you know what you are doing, you can later change this command to use a different image viewer in SimpleITK, such as ITK-Snap.)

If you already had 64-bit Anaconda installed

If you already had Anaconda x64 installed but are using a verison of Python older than 3.5, then you should upgrade to Python 3.6 using conda from a command line:

conda update conda
conda install python=3.6
conda update jupyter
conda update matplotlib
conda update scipy

Use the command line to enter these commands one at a time (they may prompt you with questions) to update python and install python versions of both VTK and SimpleITK (We need to use the clinicalgraphics channel to get vtk 7.x and to get vtk for python 3.x):

conda update conda
conda update ipython
conda install -c clinicalgraphics vtk
conda install -c simpleitk simpleitk=1.0.1

Note:  If (and only if) you get an "UnsatisfiableError" involving freetype and libpng, then do conda update freetype and then try installing simpleitk again.

Now, using the same command line, enter the command ipython. If the ipython command works, you will be told which version of python you are using and you can then use the python command quit() to exit.

Lastly, download ImageLoadingAndViewing_Basics.ipynb and place it in C:\MIMIA\Notebooks\  (Note: you might have to right-click on the link and choose Download or Save As).

WARNING: PYTHON 3.X REQUIRES PRINT() SYNTAX, edit the downloaded notebook as needed.

Note: It is highly recommend to use some form of iPython instead of "regular" python for interactive python usage. In addition to command-line iPython, iPython's QtConsole provides some additional tools, iPython's Spyder provides a "normal" MATLAB-like interface, where you can edit a python source-code file on the left and also directly run commands in iPython console(s) on the lower-right, and iPython's Jupyter Notebook mode allows for a web-browser-based mathematica-like interface with inline images and inline graphing. You can easily launch most (if not all) of these iPython environments from inside of the Anaconda-Navigator application, and you can also launch Spyder from the command line with the spyder command.

Testing Notebooks

Now try running iPython Notebook. (On mac/unix, do this from inside of your ~/MIMIA/Notebooks/ directory.) Your webbrowser should open a webpage containing a list of folders, from which you should navigate to your Notebooks folder, and then you should click on the notebook you just downloaded (ImageLoadingAndViewing_Basics-PGM). Click on the "Cell" menu, and then click on "Run All". Now, scroll to the bottom where you should see a mostly blue or purple image plot. Take a screenshot (on windows, you can press Alt-PrtScn on your keyboard; on Mac, you can either use the included Grab program or the Command-Shift-4 shortcut). You can now close your iPython Notebook.

***Email the screenshot (with the rest of your submission) to the TA.  (Be sure to use the filename mentioned at submisison checklist at the top of this page.)

Note:   If you get a runtime error about an exception thrown in sitkShow.cxx because it can't find a file or directory for the child process, then this probably means that SimpleITK can't find ImageJ. Email your TA or instructor, copying the exact error from your notebook, and also telling them exactly where/how you installed ImageJ and which version of Mac/Windows/Linux you are using.


Open an ipython prompt (see above), and then enter the following two lines:

import SimpleITK as sitk

*** Email the resulting text as a screenshot (with the rest of your submission) to the TA.

3. Compiling & Installing C++ VTK (5 points)

The VTK source code can be downloaded from on the Download page. source release ( and extact it into C:\MIMIA\. This will create the folder C:\MIMIA\VTK-8.1.0, after which you should manually create the build folder C:\MIMIA\VTKBin.

Now run the CMake GUI:

On Windows It should be in your Applications folder (or Start Menu) under CMake. At some point CMake will ask what compiler system you are using, e.g. Visual Studio 14 (64-bit).

Warning: if you installed a 64-bit version of Python, you should choose a 64-bit build, such as Visual Studio 10 Win64. WARNING: NEVER choose IA64
(unless you are absolutely sure you are using this Microsoft-abandoned, enterprise-server architecture that is not x86-64 compatible).

At the top of the CMake GUI are two fields, one for source code and one for where to build the binaries; the source code directory is the directory where VTK has been extracted (e.g. C:\MIMIA\VTK-8.1.0), and the binary directory is the directory in which you want to build (e.g. C:\MIMIA\VTKBin).

On OS X I recommend using the GUI App named CMake..., which is located in your Applications folder and is similar to the windows GUI. If you are asked to select a generator, then select the option most appropriate for the compiler you intend to use, e.g. "Xcode with default native compilers." At the top of the CMake GUI are two fields, one for source code and one for where to build the binaries; the source code directory is the directory where VTK has been extracted (e.g. ~/MIMIA/VTK-8.1.0), and the binary directory is the directory in which you want to build (e.g. ~/MIMIA/VTKBin). Note: If CMake asks you if you want to create Makefiles, you may want to choose XCode instead.

On Linux (and as an alternative on OS X) you can use CMake's command-line "GUI"/TUI tool ccmake by issuing the following command within your VTKBin directory:

    ccmake (-G Xcode) ../VTK-8.1.0 (-DCMAKE_BUILD_TYPE=RELEASE)

    IMPORTANT: Note that "../VTK-8.1.0" should be the path to the directory where you extracted VTK. Change this if necessary.

Once your CMake GUI is running, make sure that "Grouped" is checked and that "Advanced" is not checked. You now want to "configure" the system. This will cause cmake to establish environment settings for the build process. Once finished, you will be presented with a (nested) list of optional or unknown values for you to change as needed (these will typically be shown in red). 

Make sure that BUILD_SHARED_LIBS, BUILD_EXAMPLES, and BUILD_TESTING are turned off
Turn on VTK_Group_Rendering and VTK_Group_StandAlone.

Once these variables have been set, Configure again. If the "Generate" button is still grayed out, click "Configure" yet again. Finally, you should be able to generate the build environment (i.e., on Windows you "Generate" button).

On Windows, this will create a Visual Studio workspace solution named VTK.sln, in your 'VTKBin' folder, that can be used for the build. You want to build the 'ALL_BUILD' target inside it.
This will take ~10-15 minutes, maybe more depending on your system configuration. Wait for VS'10 to finish building the solution.  

Under Mac OS X or other UNIX-like systems, this should generate either a Makefile or an Xcode project that can be used for the build. If using Xcode, then build the ALL_BUILD Target (typically by pressing Command-B on the keyboard). If you are using a Makefile, simply issue the make command from within the VTKBin directory.

After using your compiler of choice to build the solution/project/Makefile that CMake just created in your VTKBin directory, then your VTKBin\lib\(Debug\)(or similar) directory will contain the compiled binaries necessary for linking to VTK.


Create a new directory, e.g. C:\MIMIA\VTKTest

Now, VTK-8.1.0 will contain an 'Examples' directory. Copy the 2 files from the Examples/Tutorial/Step6/Cxx directory out of VTK, and into the new directory C:\MIMIA\VTKTest. Create a build directory (e.g. C:\MIMIA\VTKTestBin). Run the CMake GUI with the newly created source and build directories. If CMake complains about not finding VTK, don't worry — we're about to fix it. Open up "Ungrouped Entries" and make sure that 'VTK_DIR' is set to your VTKBin directory (things might not work if it is set to a different VTK, such as one that might have been automatically installed by Anaconda). Once you are sure that the correct VTKBin directory is being used, then hit Configure/Generate. Open up the Step6 solution file (or XCode Project file) and then compile/build it using the 'All Build' option. Check the debug folder inside your build directory for an executable program named 'Cone6.exe' (or Run the Cone6 program.

If all you see is white then press the "r" key on your keyboard. Take a screenshot (on windows, you can press Alt-PrtScn on your keyboard; on Mac, you can either use the included Grab program or the Command-Shift-4 shortcut). 

***Email the screenshot (with the rest of your submission) to the TA. 

If you run into problems building VTK, and the TA cannot immediately resolve them, then please subscribe to the VTK users mailing list and ask for help.

4. Compiling & Installing C++ ITK & C++ SimpleITK (5 points)

Before we can custom compile C++ SimpleITK, we must first install git (and svn while we're at it):


SVN is a revision control system that this class will be using for homework submission. Svn may already be installed (try typping "svn --version" into a command prompt), but if svn is not already installed then svn can be easily installed using Anaconda:

conda install svn


"Git" is an advanced replacement for svn, designed for masively distributed collaborative development. (This class will actually use svn rather than git for submitting assignments, since svn is simpler.) Git is, however, the way that ITK 4.x and SimpleITK are developed, and is the only way to get the source code for custom-compiling SimpleITK, which is necessary to use SimpleITK in C++. Git may already be installed (try typping "git --version" into a command prompt), but if git is not already installed then git can be easily downloaded and installed either direclty from (currently recommended) or else using Anaconda with conda install git

On Windows, as of Feb. 5th 2018, Anaconda git on Windows has a bug involving environment variable order that prevents cloning SimpleITK below; if you installed Anaconda git on Windows, I suggest removing it using conda remove git and then downloading git directly from the git-scm URL above.

The git installer may eventually ask you about "Adjusting your PATH environment," at which point you should choose to "Run Git from the Windows Command Prompt." Everywhere else, go with the default choices.


Once git is installed, we can now use an automated process to download, compile, and install C++ ITK as needed for SimpleITK. Download the latest (relatively stable) development version of SimpleITK source code by using a command prompt to change to your MIMIA directory and then issuing a couple of git commands:

git clone --recursive
cd SimpleITK
git checkout v1.0.1 -b release101

While we're at it, now is also a good time to also check out some SimpleITK Jupyter notebooks. Again, use git from a command prompt:

git clone --recursive
git clone --recursive
git clone --recursive

After that is finished, create a place to build SimpleITK:

mkdir SITKBin

Warning: We are deliberately using the short name of SITKBin because on Windows CMake requires us to keep the total pathname to all ITK directories to be less than 50 characters each.

Now, run CMake. For the source-code directory, use SimpleITK's super-build directory, e.g. c:\MIMIA\SimpleITK\SuperBuild , and use a binary directory of c:\MIMIA\SITKBin. When you press "Configure," don't worry about any potential pop-up warnings about needing to install a Java Runtime Environment--just click OK to make the dialog disappear without installing java. After configuring, you should be able to turn off each of BUILD_EXAMPLES, BUILD_TESTING, WRAP_CSHARP, WRAP_JAVA, WRAP_LUA, WRAP_PYTHON, WRAP_R, WRAP_RUBY, and WRAP_TCL (and any other WRAP_ language flag).

On Windows, the following used to be necessary, but has probably been fixed and no longer required: Select the "Advanced" check box at the top of CMake, and then find the entry for CMAKE_EXE_LINKER_FLAGS_DEBUG and change the end of it from /INCREMENTAL to /INCREMENTAL:NO and then make the same change for both CMAKE_MODULE_LINKER_FLAGS_DEBUG and CMAKE_SHARED_LINKER_FLAGS_DEBUG.

If you are using Visual Studio 2012, you will also need to edit the entry for CMAKE_CXX_FLAGS by adding " /D_VARIADIC_MAX=10" to end end of its entry. Also note that Visual Studio 2012 must be updated to properly support variadic templates or you will get errors about std::tuple.

Configure again and then generate your build environment.

*** For the remainder of this section, you will need to maintain a reliable internet connection, possibly for hours. I recommend leaving your laptop plugged into AC power in a location with either good WiFi or an Ethernet cable. As part of the SuperBuild, CMake has configured your build environment (Visual Studio, XCode, etc.) to call other special CMake commands to automatically download and compile software as necessary to build SimpleITK. In particular, at some point ITK will be downloaded and compiled as part of SimpleITK's ALL_BUILD, and it will need a consistent internet connection for the download.

On Windows, after CMake is done, your SITKBin directory will now contain a Visual Studio solution file named SuperBuildSimpleITK.sln

Open this file in Visual Studio, select the ALL_BUILD target, and then build the solution. This will automatically download and compile ITK, etc. as needed.
NOTE: It is okay to have 1 build error that is a link error for not finding python27_d.lib--we don't need debug-mode Python code anyway.

Warning: If your code is taking 10+ hours to compile, then you may have antivirus software slowing down Visual Studio. In this case, you may want to "pause" your antivirus software until you're done compiling.

There will be a 'Debug' folder under your c:\MIMIA\SITKBin\ITK-build\lib directory. This folder  should contain a list of ITK libraries. 

Under Mac OS X or other UNIX-like systems, CMake should generate either a Makefile or an Xcode project that can be used for the build. If using Xcode, then build the ALL_BUILD Target. If you are using a Makefile, simply issue the make command from within the SITKBin directory.

If you are using Makefiles, you will need to slightly modify the above instructions, creating separate Release and Debug build directories and following the lecture slides to specify which to ccmake, something like this:

mkdir SITKBin
cd SITKBin
ccmake -DCMAKE_BUILD_TYPE=DEBUG -Module_SCIFIO=ON ../SimpleITK/SuperBuild
make (-j2)

cd ..
mkdir SITKBinRelease
cd SITKBinRelease

make (-j2)

Note about using multiple cores for make. Make will run the fastest if you use -j to specify the number of parallel jobs to match the number of cpu cores on your machine. However, if you want to use your computer for other things during the build, then I suggest instead specifying 1 less than your cores, e.g. make -j3 on a 4 core machine, so that there will be 1 readily available core for web browsing, email, etc.

Build again in Release mode

At this point, Visual Studio (and most other compilers) will have built SimpleITK and ITK with debugging turned on. For most purposes in this class, you want debugging turned on, but for the segmentation assignment you will want to speed up your code once it is well-debugged, and that requires that you have SimpleITK and/or ITK built both with and without debugging support.

On Windows to build a second, optimized copy of SimpleITK (including ITK) without debugging support in Visual Studio:

  1. Open (if necessary) your already existing Visual Studio project for SimpleITK (the one you generated from CMake, above)
  2. In top center of Visual Studio there is a drop-down menu that currently will state "Debug" mode
  3. Change drop-down menu to "Release"
  4. Build ALL_BUILD in Visual Studio

Now, in addition to ITK libraries being located in the Debug folder, there will be a second copy of ITK libraries located in the 'Release' folder of your c:\MIMIA\SITKBin\ITK-build\lib directory. Likewise, you should also have both debug and release libraries for SimpleITK.

Under Mac OS X Mavericks, You can build in Release mode by either pressing shift-command-i, or by going to the Product menu and then selecting Build For -> Profiling.

FYI, the chief reason that turning off debugging support makes your code faster is that it allows the compiler much more freedom to automatically optimize your code. For the upcoming segmentation assignment, this could make your code over 6 times faster.

***Email a screenshot showing the list of resulting files in MIMIA\SITKBin\lib{\Release} or MIMIA\SITKBin\SimpleITK-Build\lib{\Release} to the TA. (Please use whichever directory on your system that exists and contains the files, with or without the Release subdirectory as necessary.)

5. Testing C++ ITK (5 points)

At this point, from the previous super build you should already have an ITK source directory located here:


and a working installation of ITK located here:


The next instructions follow the pattern in Lecture04 to perform the ITK installation test. (Do NOT follow lecture 4's instructions to install ITK, since that is already done. Also, keep in mind to use c:\MIMIA\SITKBin\ITK instead of 'InsightToolkit-x.x.x' and to use c:\MIMIA\SITKBin\ITK-build instead of 'InsightBin' when following Lecture 4 for this part of the assignment.)

Go back to the parent directory 'c:\MIMIA'. Create two new folders called 'TestITK' and 'TestITKBin'. Next, find the 'Installation' folder in c:\MIMIA\SITKBin\ITK\Examples and copy the two files in that folder to the new folder 'TestITK'. 
After this step, copy this full path of this directory and paste it as the source directory in the CMake GUI. The full path to your 'TestITKBin' folder is where you will build the binaries. Finally, click on 'Configure'.

You may have to edit the value for ITK_DIR to point to your SITKBin/ITK-build directory, e.g. c:\MIMIA\SITKBin\ITK-build or on Mac ~/Documents/MIMIA/SITKBin/ITK-build. After setting this value, you will have to click 'Configure' again.

Clicking "Generate" or "OK" should now create 'HelloWorld.sln' in the 'TestITKBin' folder. Open this VS solution and build it. Then, in your command prompt, change to 'TestITKBin\Debug' (or equivalent) and run 'HelloWorld.exe'.
'HelloWorld.exe' is a command-line program, you should probably run it either from within Visual Studio, or from a command-prompt. 

Command-prompt might be preferable if Visual Studio closes the application file before you can visualize the result (as is sometimes the case). 

On OS X, if the build fails with errors about C++11, then you may ned to close Xcode, re-run CMake, this time turning on Advanced options and setting CMAKE_CXX_FLAGS to contain -std=c++11 . After setting this value, you will need to run Configure and Generate again, and then open the XCode project and try building again.

***Email the text output as a screenshot (with the rest of your submission) to the TA.

Final Reminder: Did you follow all the instructions at the top of this assignment for how to name your files and submit your work via a single email?

6. Rejoice

If everything is working and if you want to "jump ahead" now, then feel free to look at the official list of SimpleITK examples for C++ and Python:

If everything is not working, and if you still run into compiler/linker errors after updating your compiler system with the latest patches, then please do not hesitate to copy and paste your errors to someone (preferably the TA). If he/she can't help you, they'll find someone who can.

Good luck!