Hey Dave,

You were right. My X-Code was out of date. I updated to version 8.1, but was still running into the same problem.

The solution was to download command line tools from the apple developer site as follows:

1. Open Xcode app. 2) Click on Xcode > Open Developer Tools > More Developers Tools. That will take you to Downloads for Apple Developers web site. Use your AppStore Id to login. 3) Download Command Line Tools for your Mac OS X version.

This appears to be a common problem: eg. http://stackoverflow.com/questions/23260748/manual-install-of-xcode-command-line-tools-not-working/23319506#23319506

Thanks for your help.

Cheers.

from simpleitk.

I've seen that issue before in the past. Did you recently install or upgrade Xcode? Have you run the "xcode-select" command to set the active developer directory? If not, give that a try.

from simpleitk.

I don't use Xcode for anything, and haven't upgraded or installed it recently. I have version 7.3.1

xcode-select --version
//returns:
xcode-select version 2343.
// and I ran:
sudo xcode-select --reset
// for good luck
xcode-select --print-path
// returns:
/Applications/Xcode.app/Contents/Developer

still no luck with the PCRE build

from simpleitk.

What version of cmake are you running? As I said in that previous, closed issue, back then I worked around it by building my own copy of swig. I think, though, that the problem went away with more recent versions of cmake.

BTW, I don't use Xcode for anything either, except to install and set up the compiler, clang.

from simpleitk.

I'm glad to hear that you're figured out the solution. And it's good that we now have the answer here for others to find.

from simpleitk.

Had another tripup during the build.

When turning WRAP_PYTHON ON I got the following error:

ERROR:

CMake Error at
/Applications/CMake.app/Contents/share/cmake-3.5/Modules/FindPackageHandleStan
dardArgs.cmake:148 (message):
Could NOT find PythonLibs: Found unsuitable version "2.7.10", but required
is exact version "2.7.12" (found /usr/lib/libpython2.7.dylib)
Call Stack (most recent call first):

/Applications/CMake.app/Contents/share/cmake-3.5/Modules/FindPackageHandleStan
dardArgs.cmake:386 (_FPHSA_FAILURE_MESSAGE)

/Applications/CMake.app/Contents/share/cmake-3.5/Modules/FindPythonLibs.cmake:
265 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
/Users/markrichardson/SimpleElastix/src/CMake/sitkLanguageOptions.cmake:71
(find_package)
SuperBuild.cmake:236 (include)
CMakeLists.txt:24 (include)

SOLUTION:

1. open /Users/xxxxxx/SimpleElastix/src/CMake/sitkLanguageOptions.cmake in textwrangler
2. Change Line71 from:
   find_package ( PythonLibs ${PYTHON_VERSION_STRING} EXACT ${_QUIET_LIBRARY} )
   To:
   find_package ( PythonLibs ${PYTHON_VERSION_STRING} )

I wonder if you've run into this before, or if you have any thoughts on this one. The rest of the build ran well, and all the tests were successful.

/ /
NOTE:
python -v # returns:
/usr/local/Cellar/python/2.7.12_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site.pyc matches /usr/local/Cellar/python/2.7.12_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site.py
import site # precompiled from /usr/local/Cellar/python/2.7.12_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site.pyc

... etc ...

Cheers

from simpleitk.

Unfortunately it's not too uncommon for CMake to "automatically" find and python executable and a python library whose versions don't match or are from different installed python. You should verify that the PYTHON_EXECUTABLE and the PYTHON_LIBRARY refers to the same installed Python. Otherwise problems may occur.

Also SimpleElastix may be missing important features that SImpleITK has. Please report SimpleElastix issues in there repo first:
https://github.com/kaspermarstal/SimpleElastix

from simpleitk.

File was here:

/Users/xxxxxx/SimpleITK/src/CMake/sitkLanguageOptions.cmake

sorry for that

from simpleitk.