ENH: Software Guide updates.

Author: hjmjohnson

ITKSoftwareGuide.cmake

@@ -17,6 +17,13 @@ if(Slicer_BUILD_${PROJECT_NAME})
 endif()
 include(${ITK_USE_FILE})
 
+if( NOT IS_DIRECTORY "${ITK_SOURCE_DIR}" )
+  message(FATAL_ERROR "ITK source directory is not set :${ITK_SOURCE_DIR}:")
+endif( )
+if( NOT IS_DIRECTORY "${ITK_BINARY_DIR}" )
+  message(FATAL_ERROR "ITK build directory is not set :${ITK_BINARY_DIR}:")
+endif( )
+
 #-----------------------------------------------------------------------------
 enable_testing()
 include(CTest)

SoftwareGuide/Latex/Abstract.tex

@@ -13,13 +13,14 @@ \chapter*{Abstract}
 
 ITK is implemented in C++. It is cross-platform, using a build
 environment known as \href{http://www.cmake.org}{CMake} to manage the
-compilation process in a platform-independent way. In addition, an
-automated wrapping process
+compilation process in a platform-independent way.
+In addition, an automated wrapping process
 (\href{http://public.kitware.com/Cable/HTML/Index.html}{Cable})
 generates interfaces between C++ and interpreted programming languages
-such as \href{http://tcl.sourceforge.net}{Tcl}, 
-\href{http://java.sun.com}{Java}, and 
+such as
 \href{http://www.python.org}{Python}. This
+\href{http://tcl.sourceforge.net}{Tcl},
+\href{http://java.sun.com}{Java}, and
 enables developers to create software using a variety of programming
 languages. ITK's C++ implementation style is referred to as generic
 programming, which is to say that it uses templates so that the same
@@ -39,17 +40,16 @@ \chapter*{Abstract}
 ITK community is what helps manage the rapid evolution of the
 software.  Testing is what keeps the software stable. In ITK, an
 extensive testing process (using a system known as
-\href{http://public.kitware.com/dashboard.php}{Dart}) is in place that
+\href{http://public.kitware.com/dashboard.php?name=itk}{CDash}) is in place that
 measures the quality on a daily basis. The ITK Testing Dashboard is
 posted continuously, reflecting the quality of the software at any
 moment.
 
 This book is a guide to using and developing with ITK. The sample code
 in the
-\href{http://www.itk.org/cgi-bin/viewcvs.cgi/Examples/?root=Insight}
+\href{http://itk.org/gitweb?p=ITK.git}
 {directory} provides a companion to the material presented here.  The
 most recent version of this document is available online at
 \url{http://www.itk.org/ItkSoftwareGuide.pdf}.
 
 
-

SuperBuild.cmake

@@ -190,13 +190,6 @@ else()
     )
 endif()
 
-if( NOT IS_DIRECTORY "${ITK_SOURCE_DIR}" )
-  message(FATAL_ERROR "ITK source directory is not set :${ITK_SOURCE_DIR}:")
-endif( )
-if( NOT IS_DIRECTORY "${ITK_BINARY_DIR}" )
-  message(FATAL_ERROR "ITK build directory is not set :${ITK_BINARY_DIR}:")
-endif( )
-
 _expand_external_project_vars()
 set(COMMON_EXTERNAL_PROJECT_ARGS ${${CMAKE_PROJECT_NAME}_SUPERBUILD_EP_ARGS})
 set(extProjName ${PRIMARY_PROJECT_NAME})

SuperBuild/External_ITKv4.cmake

@@ -110,7 +110,7 @@ if(NOT ( DEFINED "${extProjName}_DIR" OR ( DEFINED "USE_SYSTEM_${extProjName}" A
     )
   ### --- End Project specific additions
   set(${proj}_REPOSITORY ${git_protocol}://itk.org/ITK.git)
-  set(${proj}_GIT_TAG 3c03e162c7e287b81115e2175898482998b50a34) #2013-01-30 New FFTW for DWIConvert with clang
+  set(${proj}_GIT_TAG 05eff7a29c1633a5462a094884646a66c0bc3410)
   ExternalProject_Add(${proj}
     GIT_REPOSITORY ${${proj}_REPOSITORY}
     GIT_TAG ${${proj}_GIT_TAG}