Skip to content

Known Issues

On this page, we document the common problems that users might encounter while using HUMMR.

CMake Problems

This section addresses various CMake-related issues that users might encounter while using HUMMR.

Updating Extern Builds

After successfully installing HUMMR using the following two steps:

cmake -S . -B build -DCMAKE_BUILD_TYPE=<Specify Debug or Release>

cmake --build build -j <nprocs>

the file structure should look like the following:

.
├── CMakeLists.txt
├── LICENSE
├── README.md
├── manual.pdf
├── build
│   ├── CMakeCache.txt
│   ├── CMakeFiles
│   ├── Makefile
│   ├── cmake_install.cmake
│   ├── hummr
│   ├── extern/
│   │   ├── CMakeCache.txt
│   │   ├── CMakeFiles
│   │   ├── CMakeLists.txt
│   │   ├── Makefile
│   │   ├── example_lib1
│   │   ├── example_lib1-prefix
│   │   ├── example_lib2
│   │   └── example_lib2-prefix
│   └── src/
├── extern/
│   ├── CMakeLists.txt
│   ├── CMakeLists.txt.in
│   ├── FindCBLAS.cmake
│   ├── FindLAPACKE.cmake
│   ├── example_lib1.zip
│   └── example_lib2.zip
├── src/
└── test_suite/

If a library in the extern/ is updated, executing the 1st installation step might not update the corresponding library in the build/extern/, which is where the libraries in extern/ are built.

In that case, please go to the build/extern/ and manually delete the folders for that library. For example, if extern/example_lib1.zip is updated and installation step 1 is executed to rebuild, and the changes aren't produced in the build/extern/example_lib1/, manually delete the following folders:

  • build/extern/example_lib1/
  • build/extern/example_lib1-prefix/

Once deleted, execute the two installation steps again. The new changes will now be available in the builds of these external libraries.