Unable to build doxygen (development branch)

[krishnakumarg1984]

When trying to build the project (at development branch current HEAD) with doxygen enabled as follows:

$ mkdir build && cd build
$ conan install .. --build missing -pr:h=default -pr:b=default -o benchmarks=on -o docs=on -o coverage=on
$ conan build ..

we get the following error:

CMake Error at cmake_files/dependencies.cmake:24 (find_package):
  By not providing "Finddoxygen.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "doxygen", but
  CMake did not find one.

  Could not find a package configuration file provided by "doxygen" with any
  of the following names:

    doxygenConfig.cmake
    doxygen-config.cmake

  Add the installation prefix of "doxygen" to CMAKE_PREFIX_PATH or set
  "doxygen_DIR" to a directory containing one of the above files.  If
  "doxygen" provides a separate development package or SDK, be sure it has
  been installed.
Call Stack (most recent call first):
  CMakeLists.txt:58 (include)


-- Configuring incomplete, errors occurred!
ERROR: conanfile.py (sopt/4.0.0): Error in build() method, line 77
        cmake.configure()
        ConanException: Error 1 while executing cmake -G "Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE="/home/krishnakumar/Documents/ucl_arc_work_docs/lexci_sopt_purify/sopt/build/conan_toolchain.cmake" -DCMAKE_INSTALL_PREFIX="/home/krishnakumar/Documents/ucl_arc_work_docs/lexci_sopt_purify/sopt/build/package" -DCMAKE_POLICY_DEFAULT_CMP0091="NEW" -DCMAKE_BUILD_TYPE="Release" "/home/krishnakumar/Documents/ucl_arc_work_docs/lexci_sopt_purify/sopt"

[tkoskela]

We had this issue recently, could you try if the notes in #338 and #335 help?

[krishnakumarg1984]

Doesn't work with the latest release of Conan 1.x series. I haven't yet read #335. Will update after trying more things.

[SJaffa]

The solution is to do sudo apt install doxygen before building. We have not added this to the general readme because most users will not be building the documentation but we do it in our github action that creates the documentation webpage.