Skip to content

error.external.build.failed

Ruslan Baratov edited this page Apr 22, 2015 · 4 revisions
What happens
  • CMake fatal error with one of the messages:
  • [hunter ** FATAL ERROR **] Configure step failed (dir: ...)
  • [hunter ** FATAL ERROR **] Build step failed (dir: ...)
Explanation
  • Build of some external package failed for some reason
What to do
Fixable errors
Windows
  • "Path too long" error with message:
The specified path, file name, or both are too long.  The fully qualified
file name must be less than 260 characters, and the directory name must be
less than 248 characters.

can be fixed by setting HUNTER_ROOT environment variable to some short path, like C:\_hunter. Alternatively you can set HUNTER_BINARY_DIR environment variable. In this case all installed packages will be kept in HUNTER_ROOT but all builds will be triggered in HUNTER_BINARY_DIR. Note that if several Hunter-ID will be send to HUNTER_BINARY_DIR they will block each other and will be build sequentially (builds in HUNTER_ROOT lock different directories so different Hunter-ID instances work in parallel). Note that the problem is about native build tool (like Visual Studio) and not in CMake. CMake already using extended-length path \\?\C:\ format (see ConvertToWindowsExtendedPath).

Mac OS X
  • Runtime application error:
Unknown class * in Interface Builder file at path *.nib

Check you have next flags linked to your target:

target_link_libraries(... "-all_load" "-ObjC")
Unfixable errors
  • File a bug report please

Clone this wiki locally