whitespace

test/unit/CMakeLists.txt

@@ -10,7 +10,8 @@ add_compile_options(${NMODL_TESTS_COMPILER_WARNING_SUPPRESSIONS})
 # =============================================================================
 # Test executables
 # =============================================================================
-add_executable(testnmodl
+add_executable(
+  testnmodl
   utils/nmodl_constructs.cpp
   utils/test_utils.cpp
   ${PROJECT_BINARY_DIR}/src/config/config.cpp
@@ -50,8 +51,10 @@ add_executable(testnmodl
   parser/parser.cpp
   printer/printer.cpp
   symtab/symbol_table.cpp
-  newton/newton.cpp ${NEWTON_SOLVER_SOURCE_FILES}
-  crout/crout.cpp ${CROUT_SOLVER_SOURCE_FILES}
+  newton/newton.cpp
+  ${NEWTON_SOLVER_SOURCE_FILES}
+  crout/crout.cpp
+  ${CROUT_SOLVER_SOURCE_FILES}
   units/lexer.cpp
   units/parser.cpp
   codegen/codegen_info.cpp
@@ -62,17 +65,15 @@ add_executable(testnmodl
   codegen/transform.cpp
   codegen/codegen_compatibility_visitor.cpp)
 
-
-target_include_directories(testnmodl PRIVATE
-    ${PYBIND11_INCLUDE_DIR} ${PYTHON_INCLUDE_DIRS}
-    ${NMODL_PROJECT_SOURCE_DIR}/test
-    ${NMODL_PROJECT_SOURCE_DIR}/src/solver
-    ${NMODL_PROJECT_SOURCE_DIR}/src/utils
-    ${NMODL_PROJECT_SOURCE_DIR}/ext/eigen)
+target_include_directories(
+  testnmodl
+  PRIVATE ${PYBIND11_INCLUDE_DIR} ${PYTHON_INCLUDE_DIRS} ${NMODL_PROJECT_SOURCE_DIR}/test
+          ${NMODL_PROJECT_SOURCE_DIR}/src/solver ${NMODL_PROJECT_SOURCE_DIR}/src/utils
+          ${NMODL_PROJECT_SOURCE_DIR}/ext/eigen)
 
 target_link_libraries(
   testnmodl
-  PUBLIC  spdlog::spdlog
+  PUBLIC spdlog::spdlog
   PRIVATE visitor
           symtab
           lexer
@@ -97,9 +98,9 @@ cpp_cc_configure_sanitizers(TARGET testnmodl)
 # See https://github.com/catchorg/Catch2/issues/2424
 string(REPLACE ";" ";ENVIRONMENT;" _environment_vars_list "${test_env}")
 # Catch2 doesn't set these environment variables when running the executable to discover tests
-# (https://github.com/catchorg/Catch2/issues/1810). This means that in builds that enable it, we
-# see errors from the LeakSanitizer during the build. These seem to be harmless because Catch2
-# does not seem to check the exit code.
+# (https://github.com/catchorg/Catch2/issues/1810). This means that in builds that enable it, we see
+# errors from the LeakSanitizer during the build. These seem to be harmless because Catch2 does not
+# seem to check the exit code.
 catch_discover_tests(testnmodl TEST_PREFIX "testnmodl/" PROPERTIES ENVIRONMENT
                      "${_environment_vars_list}")