inja/000775 001750 001750 00000000000 15110423647 013472 5ustar00matthiasmatthias000000 000000 inja/.github/000775 001750 001750 00000000000 15110423647 015032 5ustar00matthiasmatthias000000 000000 inja/.github/FUNDING.yml000664 001750 001750 00000000675 15110422543 016651 0ustar00matthiasmatthias000000 000000 # These are supported funding model platforms github: [pantor] # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2] patreon: # Replace with a single Patreon username open_collective: # Replace with a single Open Collective username ko_fi: # Replace with a single Ko-fi username tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel custom: # Replace with a single custom sponsorship URL inja/.github/workflows/000775 001750 001750 00000000000 15110423647 017067 5ustar00matthiasmatthias000000 000000 inja/.github/workflows/ci.yml000664 001750 001750 00000006070 15110422565 020206 0ustar00matthiasmatthias000000 000000 name: CI on: [push, pull_request] jobs: ci: name: ${{ matrix.name }} runs-on: ${{ matrix.os }} strategy: fail-fast: false matrix: include: - name: ubuntu-18.04-gcc-7 os: ubuntu-18.04 compiler: gcc-7 - name: ubuntu-18.04-gcc-9 os: ubuntu-18.04 compiler: gcc-9 - name: ubuntu-20.04-gcc-10 os: ubuntu-20.04 compiler: gcc-10 - name: ubuntu-20.04-gcc-11 os: ubuntu-20.04 compiler: gcc-11 - name: ubuntu-18.04-clang-5 os: ubuntu-18.04 compiler: clang-5.0 - name: ubuntu-18.04-clang-7 os: ubuntu-18.04 compiler: clang-7 - name: ubuntu-20.04-clang-9 os: ubuntu-20.04 compiler: clang-9 - name: ubuntu-20.04-clang-10 os: ubuntu-20.04 compiler: clang-10 - name: ubuntu-20.04-clang-11 os: ubuntu-20.04 compiler: clang-11 - name: ubuntu-20.04-clang-12 os: ubuntu-20.04 compiler: clang-12 - name: ubuntu-20.04-clang-11-no-exceptions os: ubuntu-20.04 compiler: clang-11 cmake_vars: "-DCMAKE_CXX_FLAGS=-fno-exceptions -DBUILD_TESTING=OFF -DBUILD_BENCHMARK=ON" - name: ubuntu-22.04 os: ubuntu-22.04 compiler: gcc - name: windows-2019 os: windows-2019 compiler: msvc - name: windows-2019-clang os: windows-2019 compiler: clang - name: windows-2019-gcc os: windows-2019 compiler: gcc - name: windows-2022 os: windows-2022 compiler: msvc # - name: macOS-11-gcc-7 # os: macOS-11 # compiler: gcc-7 # - name: macOS-11-gcc-8 # os: macOS-11 # compiler: gcc-8 - name: macOS-11-gcc-9 os: macOS-11 compiler: gcc-9 # - name: macOS-11-clang-11 # os: macOS-11 # compiler: clang-11 - name: macOS-11-clang-12 os: macOS-11 compiler: clang-12 - name: macOS-11-clang-13 os: macOS-11 compiler: clang-13 - name: macOS-12 os: macOS-12 compiler: clang steps: - uses: actions/checkout@v2 - name: Setup Cpp uses: aminya/setup-cpp@v1 with: compiler: ${{ matrix.compiler }} - name: Build & Test Debug run: | cmake -E remove_directory build cmake -B build -S . -DCMAKE_BUILD_TYPE=Debug cmake --build build -j2 cd build && ctest -j2 --output-on-failure - name: Build & Test Release run: | cmake -E remove_directory build cmake -B build -S . -DCMAKE_BUILD_TYPE=Release ${{ matrix.cmake_vars }} cmake --build build -j2 cd build && ctest -j2 --output-on-failure inja/.github/workflows/documentation.yml000664 001750 001750 00000001077 15110422565 022466 0ustar00matthiasmatthias000000 000000 name: Documentation on: push: branches: - master jobs: build-deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - name: dependencies env: dependency_packages: doxygen run: sudo apt-get update && sudo apt-get -y install ${dependency_packages} - name: build run: cd doc && doxygen ./Doxyfile - name: deploy uses: peaceiris/actions-gh-pages@v2.2.0 env: ACTIONS_DEPLOY_KEY: ${{ secrets.ACTIONS_DEPLOY_KEY }} PUBLISH_BRANCH: gh-pages PUBLISH_DIR: ./doc/html inja/.github/workflows/single-include.yml000664 001750 001750 00000001147 15110422565 022515 0ustar00matthiasmatthias000000 000000 name: Single Include on: [push, pull_request] jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - name: update single include run: | mv single_include/inja/inja.hpp single_include/inja/inja_old.hpp bash scripts/update_single_include.sh - name: check if equal working-directory: ${{runner.workspace}}/inja/single_include/ shell: bash run: | diff inja/inja.hpp inja/inja_old.hpp >/dev/null - uses: actions/upload-artifact@v3 with: name: single_include_inja path: single_include/inja/inja.hpp inja/cmake/000775 001750 001750 00000000000 15110423647 014552 5ustar00matthiasmatthias000000 000000 inja/cmake/Coveralls.cmake000664 001750 001750 00000011545 15110422543 017506 0ustar00matthiasmatthias000000 000000 # # The MIT License (MIT) # # Permission is hereby granted, free of charge, to any person obtaining a copy # of this software and associated documentation files (the "Software"), to deal # in the Software without restriction, including without limitation the rights # to use, copy, modify, merge, publish, distribute, sublicense, and/or sell # copies of the Software, and to permit persons to whom the Software is # furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in all # copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE # AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER # LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, # OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Copyright (C) 2014 Joakim Söderberg # set(_CMAKE_SCRIPT_PATH ${CMAKE_CURRENT_LIST_DIR}) # must be outside coveralls_setup() to get correct path # # Param _COVERAGE_SRCS A list of source files that coverage should be collected for. # Param _COVERALLS_UPLOAD Upload the result to coveralls? # function(coveralls_setup _COVERAGE_SRCS _COVERALLS_UPLOAD) if (ARGC GREATER 2) set(_CMAKE_SCRIPT_PATH ${ARGN}) message(STATUS "Coveralls: Using alternate CMake script dir: ${_CMAKE_SCRIPT_PATH}") endif() if (NOT EXISTS "${_CMAKE_SCRIPT_PATH}/CoverallsClear.cmake") message(FATAL_ERROR "Coveralls: Missing ${_CMAKE_SCRIPT_PATH}/CoverallsClear.cmake") endif() if (NOT EXISTS "${_CMAKE_SCRIPT_PATH}/CoverallsGenerateGcov.cmake") message(FATAL_ERROR "Coveralls: Missing ${_CMAKE_SCRIPT_PATH}/CoverallsGenerateGcov.cmake") endif() # When passing a CMake list to an external process, the list # will be converted from the format "1;2;3" to "1 2 3". # This means the script we're calling won't see it as a list # of sources, but rather just one long path. We remedy this # by replacing ";" with "*" and then reversing that in the script # that we're calling. # http://cmake.3232098.n2.nabble.com/Passing-a-CMake-list-quot-as-is-quot-to-a-custom-target-td6505681.html set(COVERAGE_SRCS_TMP ${_COVERAGE_SRCS}) set(COVERAGE_SRCS "") foreach (COVERAGE_SRC ${COVERAGE_SRCS_TMP}) set(COVERAGE_SRCS "${COVERAGE_SRCS}*${COVERAGE_SRC}") endforeach() #message("Coverage sources: ${COVERAGE_SRCS}") set(COVERALLS_FILE ${PROJECT_BINARY_DIR}/coveralls.json) add_custom_target(coveralls_generate # Zero the coverage counters. COMMAND ${CMAKE_COMMAND} -DPROJECT_BINARY_DIR="${PROJECT_BINARY_DIR}" -P "${_CMAKE_SCRIPT_PATH}/CoverallsClear.cmake" # Run regress tests. COMMAND ${CMAKE_CTEST_COMMAND} --output-on-failure # Generate Gcov and translate it into coveralls JSON. # We do this by executing an external CMake script. # (We don't want this to run at CMake generation time, but after compilation and everything has run). COMMAND ${CMAKE_COMMAND} -DCOVERAGE_SRCS="${COVERAGE_SRCS}" # TODO: This is passed like: "a b c", not "a;b;c" -DCOVERALLS_OUTPUT_FILE="${COVERALLS_FILE}" -DCOV_PATH="${PROJECT_BINARY_DIR}" -DPROJECT_ROOT="${PROJECT_SOURCE_DIR}" -P "${_CMAKE_SCRIPT_PATH}/CoverallsGenerateGcov.cmake" WORKING_DIRECTORY ${PROJECT_BINARY_DIR} COMMENT "Generating coveralls output..." ) if (_COVERALLS_UPLOAD) message("COVERALLS UPLOAD: ON") find_program(CURL_EXECUTABLE curl) if (NOT CURL_EXECUTABLE) message(FATAL_ERROR "Coveralls: curl not found! Aborting") endif() add_custom_target(coveralls_upload # Upload the JSON to coveralls. COMMAND ${CURL_EXECUTABLE} -S -F json_file=@${COVERALLS_FILE} https://coveralls.io/api/v1/jobs DEPENDS coveralls_generate WORKING_DIRECTORY ${PROJECT_BINARY_DIR} COMMENT "Uploading coveralls output...") add_custom_target(coveralls DEPENDS coveralls_upload) else() message("COVERALLS UPLOAD: OFF") add_custom_target(coveralls DEPENDS coveralls_generate) endif() endfunction() macro(coveralls_turn_on_coverage) if(NOT (CMAKE_COMPILER_IS_GNUCC OR CMAKE_COMPILER_IS_GNUCXX) AND (NOT "${CMAKE_CXX_COMPILER_ID}" STREQUAL "AppleClang")) message(FATAL_ERROR "Coveralls: Compiler ${CMAKE_C_COMPILER_ID} is not GNU gcc! Aborting... You can set this on the command line using CC=/usr/bin/gcc CXX=/usr/bin/g++ cmake ..") endif() if(NOT CMAKE_BUILD_TYPE STREQUAL "Debug") message(FATAL_ERROR "Coveralls: Code coverage results with an optimised (non-Debug) build may be misleading! Add -DCMAKE_BUILD_TYPE=Debug") endif() set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -g -O0 -fprofile-arcs -ftest-coverage") set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -g -O0 -fprofile-arcs -ftest-coverage") endmacro() inja/cmake/CoverallsClear.cmake000664 001750 001750 00000002527 15110422543 020455 0ustar00matthiasmatthias000000 000000 # # The MIT License (MIT) # # Permission is hereby granted, free of charge, to any person obtaining a copy # of this software and associated documentation files (the "Software"), to deal # in the Software without restriction, including without limitation the rights # to use, copy, modify, merge, publish, distribute, sublicense, and/or sell # copies of the Software, and to permit persons to whom the Software is # furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in all # copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE # AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER # LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, # OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Copyright (C) 2014 Joakim Söderberg # # do not follow symlinks in file(GLOB_RECURSE ...) cmake_policy(SET CMP0009 NEW) file(GLOB_RECURSE GCDA_FILES "${PROJECT_BINARY_DIR}/*.gcda") if(NOT GCDA_FILES STREQUAL "") file(REMOVE ${GCDA_FILES}) endif() inja/cmake/CoverallsGenerateGcov.cmake000664 001750 001750 00000041277 15110422543 022005 0ustar00matthiasmatthias000000 000000 # # The MIT License (MIT) # # Permission is hereby granted, free of charge, to any person obtaining a copy # of this software and associated documentation files (the "Software"), to deal # in the Software without restriction, including without limitation the rights # to use, copy, modify, merge, publish, distribute, sublicense, and/or sell # copies of the Software, and to permit persons to whom the Software is # furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in all # copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE # AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER # LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, # OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Copyright (C) 2014 Joakim Söderberg # # This is intended to be run by a custom target in a CMake project like this. # 0. Compile program with coverage support. # 1. Clear coverage data. (Recursively delete *.gcda in build dir) # 2. Run the unit tests. # 3. Run this script specifying which source files the coverage should be performed on. # # This script will then use gcov to generate .gcov files in the directory specified # via the COV_PATH var. This should probably be the same as your cmake build dir. # # It then parses the .gcov files to convert them into the Coveralls JSON format: # https://coveralls.io/docs/api # # Example for running as standalone CMake script from the command line: # (Note it is important the -P is at the end...) # $ cmake -DCOV_PATH=$(pwd) # -DCOVERAGE_SRCS="catcierge_rfid.c;catcierge_timer.c" # -P ../cmake/CoverallsGcovUpload.cmake # CMAKE_MINIMUM_REQUIRED(VERSION 2.8) # # Make sure we have the needed arguments. # if (NOT COVERALLS_OUTPUT_FILE) message(FATAL_ERROR "Coveralls: No coveralls output file specified. Please set COVERALLS_OUTPUT_FILE") endif() if (NOT COV_PATH) message(FATAL_ERROR "Coveralls: Missing coverage directory path where gcov files will be generated. Please set COV_PATH") endif() if (NOT COVERAGE_SRCS) message(FATAL_ERROR "Coveralls: Missing the list of source files that we should get the coverage data for COVERAGE_SRCS") endif() if (NOT PROJECT_ROOT) message(FATAL_ERROR "Coveralls: Missing PROJECT_ROOT.") endif() # Since it's not possible to pass a CMake list properly in the # "1;2;3" format to an external process, we have replaced the # ";" with "*", so reverse that here so we get it back into the # CMake list format. string(REGEX REPLACE "\\*" ";" COVERAGE_SRCS ${COVERAGE_SRCS}) if (NOT DEFINED ENV{GCOV}) find_program(GCOV_EXECUTABLE gcov) else() find_program(GCOV_EXECUTABLE $ENV{GCOV}) endif() # convert all paths in COVERAGE_SRCS to absolute paths set(COVERAGE_SRCS_TMP "") foreach (COVERAGE_SRC ${COVERAGE_SRCS}) if (NOT "${COVERAGE_SRC}" MATCHES "^/") set(COVERAGE_SRC ${PROJECT_ROOT}/${COVERAGE_SRC}) endif() list(APPEND COVERAGE_SRCS_TMP ${COVERAGE_SRC}) endforeach() set(COVERAGE_SRCS ${COVERAGE_SRCS_TMP}) unset(COVERAGE_SRCS_TMP) if (NOT GCOV_EXECUTABLE) message(FATAL_ERROR "gcov not found! Aborting...") endif() find_package(Git) set(JSON_REPO_TEMPLATE "{ \"head\": { \"id\": \"\@GIT_COMMIT_HASH\@\", \"author_name\": \"\@GIT_AUTHOR_NAME\@\", \"author_email\": \"\@GIT_AUTHOR_EMAIL\@\", \"committer_name\": \"\@GIT_COMMITTER_NAME\@\", \"committer_email\": \"\@GIT_COMMITTER_EMAIL\@\", \"message\": \"\@GIT_COMMIT_MESSAGE\@\" }, \"branch\": \"@GIT_BRANCH@\", \"remotes\": [] }" ) # TODO: Fill in git remote data if (GIT_FOUND) # Branch. execute_process( COMMAND ${GIT_EXECUTABLE} rev-parse --abbrev-ref HEAD WORKING_DIRECTORY ${CMAKE_SOURCE_DIR} OUTPUT_VARIABLE GIT_BRANCH OUTPUT_STRIP_TRAILING_WHITESPACE ) macro (git_log_format FORMAT_CHARS VAR_NAME) execute_process( COMMAND ${GIT_EXECUTABLE} log -1 --pretty=format:%${FORMAT_CHARS} WORKING_DIRECTORY ${CMAKE_SOURCE_DIR} OUTPUT_VARIABLE ${VAR_NAME} OUTPUT_STRIP_TRAILING_WHITESPACE ) endmacro() git_log_format(an GIT_AUTHOR_NAME) git_log_format(ae GIT_AUTHOR_EMAIL) git_log_format(cn GIT_COMMITTER_NAME) git_log_format(ce GIT_COMMITTER_EMAIL) git_log_format(B GIT_COMMIT_MESSAGE) git_log_format(H GIT_COMMIT_HASH) if(GIT_COMMIT_MESSAGE) string(REPLACE "\n" "\\n" GIT_COMMIT_MESSAGE ${GIT_COMMIT_MESSAGE}) endif() message("Git exe: ${GIT_EXECUTABLE}") message("Git branch: ${GIT_BRANCH}") message("Git author: ${GIT_AUTHOR_NAME}") message("Git e-mail: ${GIT_AUTHOR_EMAIL}") message("Git commiter name: ${GIT_COMMITTER_NAME}") message("Git commiter e-mail: ${GIT_COMMITTER_EMAIL}") message("Git commit hash: ${GIT_COMMIT_HASH}") message("Git commit message: ${GIT_COMMIT_MESSAGE}") string(CONFIGURE ${JSON_REPO_TEMPLATE} JSON_REPO_DATA) else() set(JSON_REPO_DATA "{}") endif() ############################# Macros ######################################### # # This macro converts from the full path format gcov outputs: # # /path/to/project/root/build/#path#to#project#root#subdir#the_file.c.gcov # # to the original source file path the .gcov is for: # # /path/to/project/root/subdir/the_file.c # macro(get_source_path_from_gcov_filename _SRC_FILENAME _GCOV_FILENAME) # /path/to/project/root/build/#path#to#project#root#subdir#the_file.c.gcov # -> # #path#to#project#root#subdir#the_file.c.gcov get_filename_component(_GCOV_FILENAME_WEXT ${_GCOV_FILENAME} NAME) # #path#to#project#root#subdir#the_file.c.gcov -> /path/to/project/root/subdir/the_file.c string(REGEX REPLACE "\\.gcov$" "" SRC_FILENAME_TMP ${_GCOV_FILENAME_WEXT}) string(REGEX REPLACE "\\^" ".." SRC_FILENAME_TMP ${SRC_FILENAME_TMP}) string(REGEX REPLACE "\#" "/" SRC_FILENAME_TMP ${SRC_FILENAME_TMP}) get_filename_component(SRC_FILENAME_TMP_ABSOLUTE ${SRC_FILENAME_TMP} ABSOLUTE) set(${_SRC_FILENAME} "${SRC_FILENAME_TMP_ABSOLUTE}") endmacro() ############################################################################## # Get the coverage data. file(GLOB_RECURSE GCDA_FILES "${COV_PATH}/*.gcda") message("GCDA files:") # Get a list of all the object directories needed by gcov # (The directories the .gcda files and .o files are found in) # and run gcov on those. foreach(GCDA ${GCDA_FILES}) message("Process: ${GCDA}") message("------------------------------------------------------------------------------") get_filename_component(GCDA_DIR ${GCDA} PATH) # # The -p below refers to "Preserve path components", # This means that the generated gcov filename of a source file will # keep the original files entire filepath, but / is replaced with #. # Example: # # /path/to/project/root/build/CMakeFiles/the_file.dir/subdir/the_file.c.gcda # ------------------------------------------------------------------------------ # File '/path/to/project/root/subdir/the_file.c' # Lines executed:68.34% of 199 # /path/to/project/root/subdir/the_file.c:creating '#path#to#project#root#subdir#the_file.c.gcov' # # If -p is not specified then the file is named only "the_file.c.gcov" # execute_process( COMMAND ${GCOV_EXECUTABLE} -p -o ${GCDA_DIR} ${GCDA} WORKING_DIRECTORY ${COV_PATH} ) endforeach() # TODO: Make these be absolute path file(GLOB ALL_GCOV_FILES ${COV_PATH}/*.gcov) # Get only the filenames to use for filtering. #set(COVERAGE_SRCS_NAMES "") #foreach (COVSRC ${COVERAGE_SRCS}) # get_filename_component(COVSRC_NAME ${COVSRC} NAME) # message("${COVSRC} -> ${COVSRC_NAME}") # list(APPEND COVERAGE_SRCS_NAMES "${COVSRC_NAME}") #endforeach() # # Filter out all but the gcov files we want. # # We do this by comparing the list of COVERAGE_SRCS filepaths that the # user wants the coverage data for with the paths of the generated .gcov files, # so that we only keep the relevant gcov files. # # Example: # COVERAGE_SRCS = # /path/to/project/root/subdir/the_file.c # # ALL_GCOV_FILES = # /path/to/project/root/build/#path#to#project#root#subdir#the_file.c.gcov # /path/to/project/root/build/#path#to#project#root#subdir#other_file.c.gcov # # Result should be: # GCOV_FILES = # /path/to/project/root/build/#path#to#project#root#subdir#the_file.c.gcov # set(GCOV_FILES "") #message("Look in coverage sources: ${COVERAGE_SRCS}") message("\nFilter out unwanted GCOV files:") message("===============================") set(COVERAGE_SRCS_REMAINING ${COVERAGE_SRCS}) foreach (GCOV_FILE ${ALL_GCOV_FILES}) # # /path/to/project/root/build/#path#to#project#root#subdir#the_file.c.gcov # -> # /path/to/project/root/subdir/the_file.c get_source_path_from_gcov_filename(GCOV_SRC_PATH ${GCOV_FILE}) file(RELATIVE_PATH GCOV_SRC_REL_PATH "${PROJECT_ROOT}" "${GCOV_SRC_PATH}") # Is this in the list of source files? # TODO: We want to match against relative path filenames from the source file root... list(FIND COVERAGE_SRCS ${GCOV_SRC_PATH} WAS_FOUND) if (NOT WAS_FOUND EQUAL -1) message("YES: ${GCOV_FILE}") list(APPEND GCOV_FILES ${GCOV_FILE}) # We remove it from the list, so we don't bother searching for it again. # Also files left in COVERAGE_SRCS_REMAINING after this loop ends should # have coverage data generated from them (no lines are covered). list(REMOVE_ITEM COVERAGE_SRCS_REMAINING ${GCOV_SRC_PATH}) else() message("NO: ${GCOV_FILE}") endif() endforeach() # TODO: Enable setting these set(JSON_SERVICE_NAME "travis-ci") set(JSON_SERVICE_JOB_ID $ENV{TRAVIS_JOB_ID}) set(JSON_REPO_TOKEN $ENV{COVERALLS_REPO_TOKEN}) set(JSON_TEMPLATE "{ \"repo_token\": \"\@JSON_REPO_TOKEN\@\", \"service_name\": \"\@JSON_SERVICE_NAME\@\", \"service_job_id\": \"\@JSON_SERVICE_JOB_ID\@\", \"source_files\": \@JSON_GCOV_FILES\@, \"git\": \@JSON_REPO_DATA\@ }" ) set(SRC_FILE_TEMPLATE "{ \"name\": \"\@GCOV_SRC_REL_PATH\@\", \"source_digest\": \"\@GCOV_CONTENTS_MD5\@\", \"coverage\": \@GCOV_FILE_COVERAGE\@ }" ) message("\nGenerate JSON for files:") message("=========================") set(JSON_GCOV_FILES "[") # Read the GCOV files line by line and get the coverage data. foreach (GCOV_FILE ${GCOV_FILES}) get_source_path_from_gcov_filename(GCOV_SRC_PATH ${GCOV_FILE}) file(RELATIVE_PATH GCOV_SRC_REL_PATH "${PROJECT_ROOT}" "${GCOV_SRC_PATH}") # The new coveralls API doesn't need the entire source (Yay!) # However, still keeping that part for now. Will cleanup in the future. file(MD5 "${GCOV_SRC_PATH}" GCOV_CONTENTS_MD5) message("MD5: ${GCOV_SRC_PATH} = ${GCOV_CONTENTS_MD5}") # Loads the gcov file as a list of lines. # (We first open the file and replace all occurences of [] with _ # because CMake will fail to parse a line containing unmatched brackets... # also the \ to escaped \n in macros screws up things.) # https://public.kitware.com/Bug/view.php?id=15369 file(READ ${GCOV_FILE} GCOV_CONTENTS) string(REPLACE "[" "_" GCOV_CONTENTS "${GCOV_CONTENTS}") string(REPLACE "]" "_" GCOV_CONTENTS "${GCOV_CONTENTS}") string(REPLACE "\\" "_" GCOV_CONTENTS "${GCOV_CONTENTS}") # Remove file contents to avoid encoding issues (cmake 2.8 has no ENCODING option) string(REGEX REPLACE "([^:]*):([^:]*):([^\n]*)\n" "\\1:\\2: \n" GCOV_CONTENTS "${GCOV_CONTENTS}") file(WRITE ${GCOV_FILE}_tmp "${GCOV_CONTENTS}") file(STRINGS ${GCOV_FILE}_tmp GCOV_LINES) list(LENGTH GCOV_LINES LINE_COUNT) # Instead of trying to parse the source from the # gcov file, simply read the file contents from the source file. # (Parsing it from the gcov is hard because C-code uses ; in many places # which also happens to be the same as the CMake list delimeter). file(READ ${GCOV_SRC_PATH} GCOV_FILE_SOURCE) string(REPLACE "\\" "\\\\" GCOV_FILE_SOURCE "${GCOV_FILE_SOURCE}") string(REGEX REPLACE "\"" "\\\\\"" GCOV_FILE_SOURCE "${GCOV_FILE_SOURCE}") string(REPLACE "\t" "\\\\t" GCOV_FILE_SOURCE "${GCOV_FILE_SOURCE}") string(REPLACE "\r" "\\\\r" GCOV_FILE_SOURCE "${GCOV_FILE_SOURCE}") string(REPLACE "\n" "\\\\n" GCOV_FILE_SOURCE "${GCOV_FILE_SOURCE}") # According to http://json.org/ these should be escaped as well. # Don't know how to do that in CMake however... #string(REPLACE "\b" "\\\\b" GCOV_FILE_SOURCE "${GCOV_FILE_SOURCE}") #string(REPLACE "\f" "\\\\f" GCOV_FILE_SOURCE "${GCOV_FILE_SOURCE}") #string(REGEX REPLACE "\u([a-fA-F0-9]{4})" "\\\\u\\1" GCOV_FILE_SOURCE "${GCOV_FILE_SOURCE}") # We want a json array of coverage data as a single string # start building them from the contents of the .gcov set(GCOV_FILE_COVERAGE "[") set(GCOV_LINE_COUNT 1) # Line number for the .gcov. set(DO_SKIP 0) foreach (GCOV_LINE ${GCOV_LINES}) #message("${GCOV_LINE}") # Example of what we're parsing: # Hitcount |Line | Source # " 8: 26: if (!allowed || (strlen(allowed) == 0))" string(REGEX REPLACE "^([^:]*):([^:]*):(.*)$" "\\1;\\2;\\3" RES "${GCOV_LINE}") # Check if we should exclude lines using the Lcov syntax. string(REGEX MATCH "LCOV_EXCL_START" START_SKIP "${GCOV_LINE}") string(REGEX MATCH "LCOV_EXCL_END" END_SKIP "${GCOV_LINE}") string(REGEX MATCH "LCOV_EXCL_LINE" LINE_SKIP "${GCOV_LINE}") set(RESET_SKIP 0) if (LINE_SKIP AND NOT DO_SKIP) set(DO_SKIP 1) set(RESET_SKIP 1) endif() if (START_SKIP) set(DO_SKIP 1) message("${GCOV_LINE_COUNT}: Start skip") endif() if (END_SKIP) set(DO_SKIP 0) endif() list(LENGTH RES RES_COUNT) if (RES_COUNT GREATER 2) list(GET RES 0 HITCOUNT) list(GET RES 1 LINE) list(GET RES 2 SOURCE) string(STRIP ${HITCOUNT} HITCOUNT) string(STRIP ${LINE} LINE) # Lines with 0 line numbers are metadata and can be ignored. if (NOT ${LINE} EQUAL 0) if (DO_SKIP) set(GCOV_FILE_COVERAGE "${GCOV_FILE_COVERAGE}null, ") else() # Translate the hitcount into valid JSON values. if (${HITCOUNT} STREQUAL "#####" OR ${HITCOUNT} STREQUAL "=====") set(GCOV_FILE_COVERAGE "${GCOV_FILE_COVERAGE}0, ") elseif (${HITCOUNT} STREQUAL "-") set(GCOV_FILE_COVERAGE "${GCOV_FILE_COVERAGE}null, ") else() set(GCOV_FILE_COVERAGE "${GCOV_FILE_COVERAGE}${HITCOUNT}, ") endif() endif() endif() else() message(WARNING "Failed to properly parse line (RES_COUNT = ${RES_COUNT}) ${GCOV_FILE}:${GCOV_LINE_COUNT}\n-->${GCOV_LINE}") endif() if (RESET_SKIP) set(DO_SKIP 0) endif() math(EXPR GCOV_LINE_COUNT "${GCOV_LINE_COUNT}+1") endforeach() message("${GCOV_LINE_COUNT} of ${LINE_COUNT} lines read!") # Advanced way of removing the trailing comma in the JSON array. # "[1, 2, 3, " -> "[1, 2, 3" string(REGEX REPLACE ",[ ]*$" "" GCOV_FILE_COVERAGE ${GCOV_FILE_COVERAGE}) # Append the trailing ] to complete the JSON array. set(GCOV_FILE_COVERAGE "${GCOV_FILE_COVERAGE}]") # Generate the final JSON for this file. message("Generate JSON for file: ${GCOV_SRC_REL_PATH}...") string(CONFIGURE ${SRC_FILE_TEMPLATE} FILE_JSON) set(JSON_GCOV_FILES "${JSON_GCOV_FILES}${FILE_JSON}, ") endforeach() # Loop through all files we couldn't find any coverage for # as well, and generate JSON for those as well with 0% coverage. foreach(NOT_COVERED_SRC ${COVERAGE_SRCS_REMAINING}) # Set variables for json replacement set(GCOV_SRC_PATH ${NOT_COVERED_SRC}) file(MD5 "${GCOV_SRC_PATH}" GCOV_CONTENTS_MD5) file(RELATIVE_PATH GCOV_SRC_REL_PATH "${PROJECT_ROOT}" "${GCOV_SRC_PATH}") # Loads the source file as a list of lines. file(STRINGS ${NOT_COVERED_SRC} SRC_LINES) set(GCOV_FILE_COVERAGE "[") set(GCOV_FILE_SOURCE "") foreach (SOURCE ${SRC_LINES}) set(GCOV_FILE_COVERAGE "${GCOV_FILE_COVERAGE}null, ") string(REPLACE "\\" "\\\\" SOURCE "${SOURCE}") string(REGEX REPLACE "\"" "\\\\\"" SOURCE "${SOURCE}") string(REPLACE "\t" "\\\\t" SOURCE "${SOURCE}") string(REPLACE "\r" "\\\\r" SOURCE "${SOURCE}") set(GCOV_FILE_SOURCE "${GCOV_FILE_SOURCE}${SOURCE}\\n") endforeach() # Remove trailing comma, and complete JSON array with ] string(REGEX REPLACE ",[ ]*$" "" GCOV_FILE_COVERAGE ${GCOV_FILE_COVERAGE}) set(GCOV_FILE_COVERAGE "${GCOV_FILE_COVERAGE}]") # Generate the final JSON for this file. message("Generate JSON for non-gcov file: ${NOT_COVERED_SRC}...") string(CONFIGURE ${SRC_FILE_TEMPLATE} FILE_JSON) set(JSON_GCOV_FILES "${JSON_GCOV_FILES}${FILE_JSON}, ") endforeach() # Get rid of trailing comma. string(REGEX REPLACE ",[ ]*$" "" JSON_GCOV_FILES ${JSON_GCOV_FILES}) set(JSON_GCOV_FILES "${JSON_GCOV_FILES}]") # Generate the final complete JSON! message("Generate final JSON...") string(CONFIGURE ${JSON_TEMPLATE} JSON) file(WRITE "${COVERALLS_OUTPUT_FILE}" "${JSON}") message("###########################################################################") message("Generated coveralls JSON containing coverage data:") message("${COVERALLS_OUTPUT_FILE}") message("###########################################################################") inja/cmake/config/000775 001750 001750 00000000000 15110423647 016017 5ustar00matthiasmatthias000000 000000 inja/cmake/config/injaBuildConfig.cmake.in000664 001750 001750 00000000445 15110422543 022452 0ustar00matthiasmatthias000000 000000 set(INJA_VERSION "@PROJECT_VERSION@") set(INJA_PACKAGE_USE_EMBEDDED_JSON "@INJA_PACKAGE_USE_EMBEDDED_JSON@") include(CMakeFindDependencyMacro) if(NOT INJA_PACKAGE_USE_EMBEDDED_JSON) find_dependency(nlohmann_json REQUIRED) endif() include("${CMAKE_CURRENT_LIST_DIR}/injaTargets.cmake") inja/cmake/config/injaConfig.cmake.in000664 001750 001750 00000000464 15110422543 021473 0ustar00matthiasmatthias000000 000000 @PACKAGE_INIT@ set(INJA_VERSION "@PROJECT_VERSION@") set(INJA_PACKAGE_USE_EMBEDDED_JSON "@INJA_PACKAGE_USE_EMBEDDED_JSON@") include(CMakeFindDependencyMacro) if(NOT INJA_PACKAGE_USE_EMBEDDED_JSON) find_dependency(nlohmann_json REQUIRED) endif() include("${CMAKE_CURRENT_LIST_DIR}/injaTargets.cmake") inja/doc/000775 001750 001750 00000000000 15110423647 014237 5ustar00matthiasmatthias000000 000000 inja/doc/logo-doxygen.jpg000664 001750 001750 00000027256 15110422543 017362 0ustar00matthiasmatthias000000 000000 JFIFHHExifMM*bj(1r2iHHPixelmator 3.8.52019:09:08 16:09:15,J http://ns.adobe.com/xap/1.0/ 8Photoshop 3.08BIM8BIM%ُ B~J," }!1AQa"q2#BR$3br %&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz w!1AQaq"2B #3Rbr $4%&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyzCC ?(3Inp?lW=|5䶞.N W1똎ٚgSE;x%@?ྷ]s6vxuOGײ?auwnLkE-+"o 9:uK R_i'I63-ƿ )|8_h0lVPÒP6Nݟ/[ gki |M7mai-;Gn8߈|G4o5ʦ#ml%`"cVCH%QxeN<*|13?`b/4?i__c>YCm):}3XMi<3۸7SЫ.AiG D]/񦷦7.0J<TˉU$n*-_֕Ռ##PA_ ً㯀 7ogvY$2u]O<cGMU+P-E-wQ@FkM9/'Y]_t 6F!մk yc##r$sC(YXw Ɯ.Pe|{ ^*5ݏ`HYhv26Ю.cwfbj+!nk$f62lD6[⿋%IuEk#%\Kp'_)Sn<я#V/+]~ӿOfn>_Ws>}+j1 fK)e(N?WpmԵ CBXŧL\UUU'}y57c߅)>M?T`YڮxtbN}G85f+.AgoN>2bܱ[Jn Ҽch6Ǫi,Խ|Z-9!$ u!St-*xJ="d{-gC_>me4x`MX=R_ΦRsu9$~8&W)e~tpSUxAYTۜUkqW+ ۥ#8arzu5i?Uf%ken?;o\^׉:ђt[+R<$x?'|85{  j:uԶ7 ,e; "et`@5 f7Z>HN'(>t2#>qonn-4ǹb+ ~[[zKjƗ'8Pƫ_z;mcS5t+d/?ƤRپiV nOn!uǿi7-o-Mwk-市 +S7ƈL؇ XIr9*4쬑KZnkiiCO@AQ_?IiWτ OpM'প\cD@ǽ~o3oG·Ē;p$kk *)pᦥЩpm'CsjWN%կ%+mFs(7aQK@AsCuޞt?C|G䣦?)f\#ck٫n= Q }1_#QO+I?{4 +($u?d-I\Dp6~Y]2x$m& X6NNq"fUp =#P0="A5Kh }*ȠcO)^V馿4ygB]4? Ծhwc-Η .2N@䓐yHqc|=F cl YNmQ&= s~bI4^5 P|5muf,~̫m#mfJѡ]Nm=/v"< K!3mh٢O $+iۢBoc.0z=Ufว Vv?0{ʍ[ tRlʭ=8ۣ5kN<_Vr 1[DtoF}D:q_jGͷ:E~awqM -h~hFyMOT{ ~W%gv{G#G_R?OgOU}\qnuWW//cO"Mߑ$w-l+V WWįDokPJ ^#ֺluH_^?[U++0Ѩ)eIw:g#[oW{'5638 D?*Ã?tO} ɮ?[/T񆿤xMNI 9bM#+G,I*dg @9Th3 .:' ]w-kƓ^Q|]xQ $kX&Se`x#=?'n_/CSf/|+Vg7W˛$k\#"$c|J5;evOqm  ( Y (|^C5WHFx'A/fY9&f SJJWos(bՄQ:~Ȓ<ű'VǷaElj5=R?gO1= _i9NAZ7'ii'Z(|c3__Q CH|=_5`-JBxXp!6vWw^__3O{H??}#1ҥF|K^&G_Nm/UWÓ,^Ge'RK$P{&u sYIJl`80k~ØW2r{ a}͕ssWIGjO&M{1-D*4 $HZoki([R6r.$92K è&[ϞRgkLkGQdžhv]J&x_Skux#';J'nlg~_R/BV&P$s aƪmTb޽1bɬX>sUD6^5O=;f :b>_'߄~ x]VwVm/>QI 8 S/FO 17(CGe<.;Tk7K{zV%=*u[7MJ÷Mkw3Y3F*c9)Jgk!B!3SΆY˝IiW_@/τ5:뉡(MRhRKI&`^f`?~$i[EcxaXtOm}o;v~޵X vgsW5:zl:tjKRg6_)tvq1x,)҅eIK"ǑmO3IzিE?(/_ۻ~G|o8|GY66FZK [H>6VBvs1 r}+qU&5Q~u/ߴE~5j{,~%&tITt%222&s^/0LK$~$#?W߷?ZyKHhj&:tZ>Y[%|T3F/O.➏s:tJݬ~fO>!S__ۯ ?P?_4J#\{x_SRkLql*so6>qT6#ms᷄(;֍6&6y]M$yܱNFP˨ w˚+GI0)sPqџs& A.wǃV|AGM.a;;y]⁈\ԟ +?敧xkxs0]|<,Ւ VpZO"._ʐ+,JA =x1x3 AJKTr|۱q_SO/ 2V x@tK+uIixyoskR)2ґ""TMʹ3ֿS\KyZT~]ęs Qd?M8&; /JgXC)$dQ^A7N[ᖛN8ɹe gI3埶|qO)nmo-eeYe^)D9d|=Ib"ۣ }Si,nϩyO%5HSǫ_ #̃,?o_&EC\Ӯ̑#t*QKţ>'_WMz., ߩka$4 ʹ,XG|P P^VߡڒG {Gi5k(LT@hUiV:mi#-~GU@zpo_r(AIQ^(k.ኅpCA*2i/t:G'%22eB$1ݎ% _e)˞~IQU7~J>iy4ȡjJjq-G? <hg?tGb8UFUbΎ 7zpK$D)F:Xny4EXF=:nsFNAjZ( E._ j5xc[:x^[BSh S%.O5?5⯊ I>#C>[ܯ9Ey Z\iy)k#*3=?wOχZICn&;I=K49嘚 +ЄU)%d4)U nNQ@F+75%]@<K\Mol5ocoiV5W(jX04)!SwH`@*)RFXd*(9X('LmI0-tq*z+ ;pKX1wHj^((inja/doc/logo.jpg000664 001750 001750 00000050407 15110422543 015701 0ustar00matthiasmatthias000000 000000 JFIFHHExifMM*bj(1r2iHHPixelmator 3.62017:08:15 20:08:32Ԡt http://ns.adobe.com/xap/1.0/ 8Photoshop 3.08BIM8BIM%ُ B~t" }!1AQa"q2#BR$3br %&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz w!1AQaq"2B #3Rbr $4%&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyzCC ?*1I4B[Hr@CJA Cn&?'t%ճJx:.C7shvOidHvbV$P3#}RGI @ky'7% _؟88J[+Ź*v+y%՟R,cH&#وaG?f7C/uXZK^Qąrd&@3~2 oQ-hP@KP{5~_N-I%c|1)Qg?QPԤڑN㚊r~5y&?OzaIjRo(dYX"%_|I|#̚gP\s޾jz!EUQEQEQE4CI@nw > lncmNA>js0Y@YCK;3,qF$0RwN~Қ4 >x+LĤگo8Z@+2#w3^!`䣈fqqi&o{WS>5|b &ѴoxsRKv_uۭĥcU2 _nO[v]ynkCiBWF|T*EEPEPEPEPX~#l<=ګlFĻ3[?3q?luehW''*ԧ:JIW%(c_S~[#/m'țUe?+4q) y#'aBA'5Ǻ7]Tm%kkK[g3F*8#־i}CN: l7$X'1_KxZrwIZ9):wӲ>_IBHnm6kp+?OŸxbKmN8ɴEDWJeFydf5>VAm洼skp$P' <Ժ_[nu!Dr(J-_chօ,6> _y_2>aIrdסxg ut'XcB#$K2G*&)iIOR8˛h!{dE%Yl9Q㑡7Wddu!U9d`^%Y(9FϐYZc;@|5ɩxI$]ulǁy=eObyoqjZ|Iduei\qjHp*:x)_߆u/hV-tC)?xUtrF7.}V~ 4 ]("E*"ܶy$6o_տ=:{Y/ן^QF^=k ɵa=0zVVv0{H5Q@:U+ǛڟX+ɾ:x!~%e]D0+o57?ٯ,I?Q^/tT㺄#0T~O?؃,(f<{^;iǯi'ݑ*HiW ㇯L{W_bۃ67GW O5:ξ+i~g00JP9)"SPF*X*3(:0MvMG1j tRaHG T$pWIsƖpt ߇ڮ͆-.௞l3lG rk?h_ٻGW7x~T}3YgD#9cG*t!c^>y}s <:vˌ{hr#w ?=?Z sǟ exV_hrnnO+7c[x]]eoػN Ҳj3iM3ckBY#ţNoD}Z RI S׏X:+HIEFJyb9Z)2Q@&;6NKoj@8"_xDk}G\0ŭ@lˑym⹎mjI(| f-??G̟Oo__Bj:+\h'2O  r>־xs;ۻgn_1wIE! u=S]TeH1Z( ( c?Z}03,YʹI Rz` zgE.XIP&OB | eIb}¾O#N}NE} W-r-$7|7Kf~=V)Ӯ+8du|cɴxsJaH+sVI?2xzO;/w tSVrʧdļvP#Kd-QZ) -!8?Ҁ>a?h cRGX>MFng}2Gt,Mn$` |'`0*Kc)UkGl &\کBб<϶-c?m;fC]SzFN-/m,Gεɖ9RY)J1D1ѓ3 ?<[Oq1:usU#fg;/k $} akuα;IഇO{.X&ҀpxajWfwVi ZxLӯN,,3Y^[#= <ƍJeN> Aڟ%c(nJ2 ]B^>Y S3)B <R#=zVx?և~3ᯏ_<7& cIdh0ι,mG,m*T+צg__6_>ݻ~X9m=N1_ҫs5' ̏s?ڃ xt:| 7i֚ziWY,Smi0VQo iVڢrxAq9s_O"~5|5W{5OCxYIr{f$n#H,[xoKBRȘcpr:_Գ,~w[{[XmN~Ru^3_<;D-k_bݗaxE-8pA@۟ƿ#1Q $~$?pa_qcWJ3Q3<<;+~~7<[e}iΡ[;Mnc1C}Abg$3_Ɨğ: ß !8MZ_q"D0s2Bki_~k $ѯ4=F o{ C Ǯ8=Gj)_Ow?c"~3ʖׄOF"[h5HLἷ &*ŸdU?=7R 8#/poh'|!oeT57[o*_ڤ'-- G%` gZ5 Údw:44ݶ-t/!gqS G8\i[MeHX܎Dl]cƿk e9\`;$nLam@4Ňk{8μFyb3>$xgץAFoZ067Vs\HH>*ǫ>Ú3}ir~oN? iS -FN: [99̘>g@1``ztӷܿۛs"x6⎁_-I ]qݐe=GF0U2<^?Q#b?X~Cٻv'ǿh4ZgQbRAդ|*N;;u tF1W%O?>ź ̢eAXc նx3껙wjt=NYҠI )>5ޝIs_ӇEyvӑv__%Ŀ^94+7 gW '< dRɐdo~=k4 J#;Ń^@v.:l,OY잝}.~`m!א=}18>k7x 0hLLcu +|c]5cs_m~,| }s,r/i3rq d:V,wd_/*?\?}_}jUg1L3k2]-QLAEP_[%QxB|],l_(Pi-Rh_̷N'׷>w_ԟW?io3wGQ+k8#O_^#Ҋ̚Usr֑ t7?BnZ#'JlP}q5?B}_KeS_-Gu +e=oQ;_ <9O|.['nN7-7V䔆{ 0x+l/Io_Kg? <r _K2oZG1!;:k@ ^A52}>!}h_@o¿y><1Ȍ] E?)%+4[ok=n~@W_({i#>OkW>+}Z>~ZD1z*§/SLi&9 8'^[O$j? xo]4kɠ\2;(82wq_?P?.7  aMCm~ ӋPjw2Y++,Lv^V6q4]^H%3KM4!෍aG(Uֿ?s7Ɨ/ Bmkm͵ė;Nvi1|v˙&il8,!P?BO5|A1nǙS<X~MO-aAZWEr~è=hGzg:#__o~QOKmÿKƒxGa֬W+"J$7] s_`c&;F. 9 F'ItF?o~;5 _М$>RgQE}Q@F<~%E'c˯ne5@nEc٭$c9(*qW>`H$#on+g !|5s-[ٌrL%b!0BaKFpM~Sq:UO=8/'Px}3,~s~|."[kFrKދsԜst=SNSd$hnR=Xs'BMywp䘠o&kHb[x$qDU8ǥD}ʥ*M}ƺ?jYo:㡯+ntO]li$YuK'~R(PrG3+m*X4=U(.vXTZ?FEy_E?'Y#)3:?XTuXlZ|0ܮ "+_UW̟?G?8e8_+?p7tOdpDv$fuQzz'S}s¶?&_?}~K/t)e}S`FȩY߱2AEV ( ?޿ uZ--~]jnşԥΧ5@ָ'l=OFchS:`*~\ o+}DdY@G_W Ёq_C*fx}&Y.ɚAW(ۊSSrE+JGݳ$#$`ߖ݌ ~_mï6?붧_Ah<8x82{~Nc_ 2S\VW>bO؏cT]cc'_F+6[rt?o:D5MWNNZ?^|35MWx887U2R])+O3%/ſ;Ow_gJ_wGkoZ?ҿGO FO_TS+'^K/X']?ao|W#9m|)% WWA!#zکyَh<3\_\\=ķwwn.=y31$Emu2A3$܊"c:|GQÜMʴG'?!C?6+[^ۇq;""(B7?}/75ҨuI/iFcݷd濘6i?>(wCPҠ7I+XƉuu2ZI#U{.١qJc<.۳=s-< j$vUBݭO bٯE7V z4ooOАHC댊Tq%z?՟k|(CSZk7wfӤYf }W%MƧ1/SrWsߦ!=1-dF:T?/5>;iψ|9qNW_עj׎,6gmS[]/)3 <_RWq Ac ?*+GDΣ,p3?Q|8~$Ym,aH`C?GcyF 96ܕJ W9A:彝|=̋/՘)geE _[j63H%@ k) +8N\ݯ~FM_3~ؠ٧X$Ҿ4ITGJo*I%]?Le!^e>yB t?]HݳqZiuo{d::܂uqֺ$2eu4~CTŏbGo/|1=g[/B/^XHn*H&OW|3 CiR~Ky0YȨN &GdWj^i:\B6$XReYX<q޾`#c_?UUGl xp|d*u9QcU*ݳ&g< ^߅?,|"}|KK,Na}`<*xQxc:YcUz#̾Aisw~>-x7JuE+8fd3vHC_'{X;t?Q'*3h嶻~,#մ٭|m>Hxê ƏxOH-mm.˞5) .bQ/~gbK<'' #v3erQ,,??x?|}'uH%wB졸@#q#K 0)4n O&W?`~4Is?iZu{H" mtGӿbHP>|?x:+<g.m&[xf 9%֬@Mio" J^FIo3 ^~߱gxjh-MxmkzT9+ L22+мk7֡FsTj?V)+BșdЗEvoҾ`bS?hpd۶s,$f9|8j.-yROKՏ}fƗ5oiyjFE,%ՀVc:@@X,b ^a*(ZY6zž~ϲ~0y_׊kG~c,RBC5Ɠ[pX n3m2ﺾO-E_dr:dKc?6k~=WРfc^0H\bO"8g;޷ǺeƑOjR:zl;]q$NIcet, ])5ǟ'QQxп |-VEZ[עλ$⻱SJG:g% BZO?>_GZE%eh7~q  2 _.'ms~ n;/^W= ]*ʜӶi"g:Y<OIW =470G(t[ !f$uϦk'p[hx8?j<}_V~5P;?/%(#+ ~:<ͪ=Ƭ-Ԭ?m}g޿|4ʎE=QCIF2ę tUq+UIqO~ մJ5fFk))RAi8jBJ{&=GR)>aWCT[$I"g>KLxOWkJ%V6Kʿ٢HXЍ=5V0}%XO\gDf/ٗ wZv]̀@ރNN߄/ xRGu=DX.?&=2a[̱5Vэ<hoR^GE~X|kM=.ݛDם%m~W>UlR+hVNiz儺N7V淸A$r)ꬭE| G?僜e_ghxO ue/SB8V^r;gм+s⯁[MfiU2Xv<5-O'o\IwGAN|2op}DRQ_K%^k;yx*q62y Iٟ"7<]sjZ.r$Ԯ$*x,U8+ wW'fkKKKu=4@ܓޝ0<<Լ]H Kx3' 0k %YU.|~Gy8cY%t58~g j^Ik0VGR*G=j꜌5ZUglg'??//=!7s6,u<fUt⿪?m;}:Rã)<`Q_ {Wk j:ލyQL1(?urի׍8׋'*q+Ѧ~OpgVU0V}:bƝ'G_,O*(bWe.t6W7ڎzufᳺ{^B[^BǞ_3/t1F둚?\>s`Z;xm ȯ\[Zmy#˗ fe= ٻGmUFNI2Y<G@qῆWmŶ .IrK1$1%$ɮ z ep jRg} R r!ԄsZ+;=N~`(0h_>iZ6:Bq@aZ(=E-!V{{H8RH*3@+~l? h<5jjlv$wJmc HԆ^ }=}|D>+|&o]Eϙk)kwuϥ[Vv2G 6YH;ЂXn _ żUW.:|yYa:M(>m_(>~˾.|3]à^&K -QJ d  ݮokʲ$+%|CÁֳ#ZCr6ћhs3ϡg?w|Qk٫gP| lm-֫0[8cL(P|WgxTѥqR劣_KB~|7i|O5/D^4q쑀zp.9޿_J9>_wC6flmCD7iv'Ln6yfɵq.8#LφC\մx-Xv!ڽ,p;5gDG( d'gQ5CDOG?>ND3ô#bYffc$I<տ'⏏::P׺k@A6CH>T\KC|UZiuDC#2 -}igeCj8P:vD1yEdʵ=${\\Ci֚>aK 1 *Z-k֝(*0VKD~m{V;!9g+&,\ʑHs(g޿{&u il#8KI i*z ҿ;@kxn5w28;=o oWV`;Q濚k9yv*ֽ/qXЫ}̻Wi$f9a{SLpzkK$hw(N6y>qKEQEKMxZ<i(((((((U`^~oe~$3&pKqhS#X_Q}jyjS QW?`O؃s>:Qm+9O}WSK,lmc$%"*VQU8ǵH),((((()3cږ:|ԕLnvEPAzQ$'jt((inja/doc/logo.svg000664 001750 001750 00000030635 15110422543 015721 0ustar00matthiasmatthias000000 000000 inja/doc/support.md000664 001750 001750 00000000433 15110422543 016267 0ustar00matthiasmatthias000000 000000 @page support_page Support If you have questions or issues regarding the use of doxygen, please use the Github [Issue Tracker](https://github.com/pantor/inja/issues). You can always contribute by helping with programming, testing and filing bug reports, and improving documentation!inja/doc/Doxyfile000664 001750 001750 00000323452 15110422565 015754 0ustar00matthiasmatthias000000 000000 # Doxyfile 1.8.14 # This file describes the settings to be used by the documentation system # doxygen (www.doxygen.org) for a project. # # All text after a double hash (##) is considered a comment and is placed in # front of the TAG it is preceding. # # All text after a single hash (#) is considered a comment and will be ignored. # The format is: # TAG = value [value, ...] # For lists, items can also be appended using: # TAG += value [value, ...] # Values that contain spaces should be placed between quotes (\" \"). #--------------------------------------------------------------------------- # Project related configuration options #--------------------------------------------------------------------------- # This tag specifies the encoding used for all characters in the config file # that follow. The default is UTF-8 which is also the encoding used for all text # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv # built into libc) for the transcoding. See # https://www.gnu.org/software/libiconv/ for the list of possible encodings. # The default value is: UTF-8. DOXYFILE_ENCODING = UTF-8 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by # double-quotes, unless you are using Doxywizard) that should identify the # project for which the documentation is generated. This name is used in the # title of most generated pages and in a few other places. # The default value is: My Project. PROJECT_NAME = "Inja" # The PROJECT_NUMBER tag can be used to enter a project or revision number. This # could be handy for archiving the generated documentation or if some version # control system is used. PROJECT_NUMBER = 3.4.0 # Using the PROJECT_BRIEF tag one can provide an optional one line description # for a project that appears at the top of each page and should give viewer a # quick idea about the purpose of the project. Keep the description short. PROJECT_BRIEF = "A Template Engine for Modern C++" # With the PROJECT_LOGO tag one can specify a logo or an icon that is included # in the documentation. The maximum height of the logo should not exceed 55 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy # the logo to the output directory. PROJECT_LOGO = "./logo-doxygen.jpg" # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path # into which the generated documentation will be written. If a relative path is # entered, it will be relative to the location where doxygen was started. If # left blank the current directory will be used. OUTPUT_DIRECTORY = # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub- # directories (in 2 levels) under the output directory of each output format and # will distribute the generated files over these directories. Enabling this # option can be useful when feeding doxygen a huge amount of source files, where # putting all generated files in the same directory would otherwise causes # performance problems for the file system. # The default value is: NO. CREATE_SUBDIRS = NO # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII # characters to appear in the names of generated files. If set to NO, non-ASCII # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode # U+3044. # The default value is: NO. ALLOW_UNICODE_NAMES = NO # The OUTPUT_LANGUAGE tag is used to specify the language in which all # documentation generated by doxygen is written. Doxygen will use this # information to generate all constant output in the proper language. # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese, # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States), # Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian, # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages), # Korean, Korean-en (Korean with English messages), Latvian, Lithuanian, # Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian, # Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish, # Ukrainian and Vietnamese. # The default value is: English. OUTPUT_LANGUAGE = English # If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member # descriptions after the members that are listed in the file and class # documentation (similar to Javadoc). Set to NO to disable this. # The default value is: YES. BRIEF_MEMBER_DESC = YES # If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief # description of a member or function before the detailed description # # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the # brief descriptions will be completely suppressed. # The default value is: YES. REPEAT_BRIEF = YES # This tag implements a quasi-intelligent brief description abbreviator that is # used to form the text in various listings. Each string in this list, if found # as the leading text of the brief description, will be stripped from the text # and the result, after processing the whole list, is used as the annotated # text. Otherwise, the brief description is used as-is. If left blank, the # following values are used ($name is automatically replaced with the name of # the entity):The $name class, The $name widget, The $name file, is, provides, # specifies, contains, represents, a, an and the. ABBREVIATE_BRIEF = "The $name class" \ "The $name widget" \ "The $name file" \ is \ provides \ specifies \ contains \ represents \ a \ an \ the # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then # doxygen will generate a detailed section even if there is only a brief # description. # The default value is: NO. ALWAYS_DETAILED_SEC = NO # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all # inherited members of a class in the documentation of that class as if those # members were ordinary class members. Constructors, destructors and assignment # operators of the base classes will not be shown. # The default value is: NO. INLINE_INHERITED_MEMB = NO # If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path # before files name in the file list and in the header files. If set to NO the # shortest path that makes the file name unique will be used # The default value is: YES. FULL_PATH_NAMES = YES # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path. # Stripping is only done if one of the specified strings matches the left-hand # part of the path. The tag can be used to show relative paths in the file list. # If left blank the directory from which doxygen is run is used as the path to # strip. # # Note that you can specify absolute paths here, but also relative paths, which # will be relative from the directory where doxygen is started. # This tag requires that the tag FULL_PATH_NAMES is set to YES. STRIP_FROM_PATH = # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the # path mentioned in the documentation of a class, which tells the reader which # header file to include in order to use a class. If left blank only the name of # the header file containing the class definition is used. Otherwise one should # specify the list of include paths that are normally passed to the compiler # using the -I flag. STRIP_FROM_INC_PATH = # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but # less readable) file names. This can be useful is your file systems doesn't # support long names like on DOS, Mac, or CD-ROM. # The default value is: NO. SHORT_NAMES = NO # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the # first line (until the first dot) of a Javadoc-style comment as the brief # description. If set to NO, the Javadoc-style will behave just like regular Qt- # style comments (thus requiring an explicit @brief command for a brief # description.) # The default value is: NO. JAVADOC_AUTOBRIEF = NO # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first # line (until the first dot) of a Qt-style comment as the brief description. If # set to NO, the Qt-style will behave just like regular Qt-style comments (thus # requiring an explicit \brief command for a brief description.) # The default value is: NO. QT_AUTOBRIEF = NO # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a # multi-line C++ special comment block (i.e. a block of //! or /// comments) as # a brief description. This used to be the default behavior. The new default is # to treat a multi-line C++ comment block as a detailed description. Set this # tag to YES if you prefer the old behavior instead. # # Note that setting this tag to YES also means that rational rose comments are # not recognized any more. # The default value is: NO. MULTILINE_CPP_IS_BRIEF = NO # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the # documentation from any documented member that it re-implements. # The default value is: YES. INHERIT_DOCS = YES # If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new # page for each member. If set to NO, the documentation of a member will be part # of the file/class/namespace that contains it. # The default value is: NO. SEPARATE_MEMBER_PAGES = NO # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen # uses this value to replace tabs by spaces in code fragments. # Minimum value: 1, maximum value: 16, default value: 4. TAB_SIZE = 4 # This tag can be used to specify a number of aliases that act as commands in # the documentation. An alias has the form: # name=value # For example adding # "sideeffect=@par Side Effects:\n" # will allow you to put the command \sideeffect (or @sideeffect) in the # documentation, which will result in a user-defined paragraph with heading # "Side Effects:". You can put \n's in the value part of an alias to insert # newlines (in the resulting output). You can put ^^ in the value part of an # alias to insert a newline as if a physical newline was in the original file. ALIASES = # This tag can be used to specify a number of word-keyword mappings (TCL only). # A mapping has the form "name=value". For example adding "class=itcl::class" # will allow you to use the command class in the itcl::class meaning. TCL_SUBST = # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources # only. Doxygen will then generate output that is more tailored for C. For # instance, some of the names that are used will be different. The list of all # members will be omitted, etc. # The default value is: NO. OPTIMIZE_OUTPUT_FOR_C = NO # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or # Python sources only. Doxygen will then generate output that is more tailored # for that language. For instance, namespaces will be presented as packages, # qualified scopes will look different, etc. # The default value is: NO. OPTIMIZE_OUTPUT_JAVA = NO # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran # sources. Doxygen will then generate output that is tailored for Fortran. # The default value is: NO. OPTIMIZE_FOR_FORTRAN = NO # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL # sources. Doxygen will then generate output that is tailored for VHDL. # The default value is: NO. OPTIMIZE_OUTPUT_VHDL = NO # Doxygen selects the parser to use depending on the extension of the files it # parses. With this tag you can assign which parser to use for a given # extension. Doxygen has a built-in mapping, but you can override or extend it # using this tag. The format is ext=language, where ext is a file extension, and # language is one of the parsers supported by doxygen: IDL, Java, Javascript, # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran: # FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran: # Fortran. In the later case the parser tries to guess whether the code is fixed # or free formatted code, this is the default for Fortran type files), VHDL. For # instance to make doxygen treat .inc files as Fortran files (default is PHP), # and .f files as C (default is Fortran), use: inc=Fortran f=C. # # Note: For files without extension you can use no_extension as a placeholder. # # Note that for custom extensions you also need to set FILE_PATTERNS otherwise # the files are not read by doxygen. EXTENSION_MAPPING = # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments # according to the Markdown format, which allows for more readable # documentation. See http://daringfireball.net/projects/markdown/ for details. # The output of markdown processing is further processed by doxygen, so you can # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in # case of backward compatibilities issues. # The default value is: YES. MARKDOWN_SUPPORT = YES # When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up # to that level are automatically included in the table of contents, even if # they do not have an id attribute. # Note: This feature currently applies only to Markdown headings. # Minimum value: 0, maximum value: 99, default value: 0. # This tag requires that the tag MARKDOWN_SUPPORT is set to YES. TOC_INCLUDE_HEADINGS = 0 # When enabled doxygen tries to link words that correspond to documented # classes, or namespaces to their corresponding documentation. Such a link can # be prevented in individual cases by putting a % sign in front of the word or # globally by setting AUTOLINK_SUPPORT to NO. # The default value is: YES. AUTOLINK_SUPPORT = YES # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want # to include (a tag file for) the STL sources as input, then you should set this # tag to YES in order to let doxygen match functions declarations and # definitions whose arguments contain STL classes (e.g. func(std::string); # versus func(std::string) {}). This also make the inheritance and collaboration # diagrams that involve STL classes more complete and accurate. # The default value is: NO. BUILTIN_STL_SUPPORT = NO # If you use Microsoft's C++/CLI language, you should set this option to YES to # enable parsing support. # The default value is: NO. CPP_CLI_SUPPORT = NO # Set the SIP_SUPPORT tag to YES if your project consists of sip (see: # https://www.riverbankcomputing.com/software/sip/intro) sources only. Doxygen # will parse them like normal C++ but will assume all classes use public instead # of private inheritance when no explicit protection keyword is present. # The default value is: NO. SIP_SUPPORT = NO # For Microsoft's IDL there are propget and propput attributes to indicate # getter and setter methods for a property. Setting this option to YES will make # doxygen to replace the get and set methods by a property in the documentation. # This will only work if the methods are indeed getting or setting a simple # type. If this is not the case, or you want to show the methods anyway, you # should set this option to NO. # The default value is: YES. IDL_PROPERTY_SUPPORT = YES # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC # tag is set to YES then doxygen will reuse the documentation of the first # member in the group (if any) for the other members of the group. By default # all members of a group must be documented explicitly. # The default value is: NO. DISTRIBUTE_GROUP_DOC = NO # If one adds a struct or class to a group and this option is enabled, then also # any nested class or struct is added to the same group. By default this option # is disabled and one has to add nested compounds explicitly via \ingroup. # The default value is: NO. GROUP_NESTED_COMPOUNDS = NO # Set the SUBGROUPING tag to YES to allow class member groups of the same type # (for instance a group of public functions) to be put as a subgroup of that # type (e.g. under the Public Functions section). Set it to NO to prevent # subgrouping. Alternatively, this can be done per class using the # \nosubgrouping command. # The default value is: YES. SUBGROUPING = YES # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions # are shown inside the group in which they are included (e.g. using \ingroup) # instead of on a separate page (for HTML and Man pages) or section (for LaTeX # and RTF). # # Note that this feature does not work in combination with # SEPARATE_MEMBER_PAGES. # The default value is: NO. INLINE_GROUPED_CLASSES = NO # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions # with only public data fields or simple typedef fields will be shown inline in # the documentation of the scope in which they are defined (i.e. file, # namespace, or group documentation), provided this scope is documented. If set # to NO, structs, classes, and unions are shown on a separate page (for HTML and # Man pages) or section (for LaTeX and RTF). # The default value is: NO. INLINE_SIMPLE_STRUCTS = NO # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or # enum is documented as struct, union, or enum with the name of the typedef. So # typedef struct TypeS {} TypeT, will appear in the documentation as a struct # with name TypeT. When disabled the typedef will appear as a member of a file, # namespace, or class. And the struct will be named TypeS. This can typically be # useful for C code in case the coding convention dictates that all compound # types are typedef'ed and only the typedef is referenced, never the tag name. # The default value is: NO. TYPEDEF_HIDES_STRUCT = NO # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This # cache is used to resolve symbols given their name and scope. Since this can be # an expensive process and often the same symbol appears multiple times in the # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small # doxygen will become slower. If the cache is too large, memory is wasted. The # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536 # symbols. At the end of a run doxygen will report the cache usage and suggest # the optimal cache size from a speed point of view. # Minimum value: 0, maximum value: 9, default value: 0. LOOKUP_CACHE_SIZE = 0 #--------------------------------------------------------------------------- # Build related configuration options #--------------------------------------------------------------------------- # If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in # documentation are documented, even if no documentation was available. Private # class members and static file members will be hidden unless the # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES. # Note: This will also disable the warnings about undocumented members that are # normally produced when WARNINGS is set to YES. # The default value is: NO. EXTRACT_ALL = NO # If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will # be included in the documentation. # The default value is: NO. EXTRACT_PRIVATE = NO # If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal # scope will be included in the documentation. # The default value is: NO. EXTRACT_PACKAGE = NO # If the EXTRACT_STATIC tag is set to YES, all static members of a file will be # included in the documentation. # The default value is: NO. EXTRACT_STATIC = NO # If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined # locally in source files will be included in the documentation. If set to NO, # only classes defined in header files are included. Does not have any effect # for Java sources. # The default value is: YES. EXTRACT_LOCAL_CLASSES = YES # This flag is only useful for Objective-C code. If set to YES, local methods, # which are defined in the implementation section but not in the interface are # included in the documentation. If set to NO, only methods in the interface are # included. # The default value is: NO. EXTRACT_LOCAL_METHODS = NO # If this flag is set to YES, the members of anonymous namespaces will be # extracted and appear in the documentation as a namespace called # 'anonymous_namespace{file}', where file will be replaced with the base name of # the file that contains the anonymous namespace. By default anonymous namespace # are hidden. # The default value is: NO. EXTRACT_ANON_NSPACES = NO # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all # undocumented members inside documented classes or files. If set to NO these # members will be included in the various overviews, but no documentation # section is generated. This option has no effect if EXTRACT_ALL is enabled. # The default value is: NO. HIDE_UNDOC_MEMBERS = NO # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all # undocumented classes that are normally visible in the class hierarchy. If set # to NO, these classes will be included in the various overviews. This option # has no effect if EXTRACT_ALL is enabled. # The default value is: NO. HIDE_UNDOC_CLASSES = NO # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend # (class|struct|union) declarations. If set to NO, these declarations will be # included in the documentation. # The default value is: NO. HIDE_FRIEND_COMPOUNDS = NO # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any # documentation blocks found inside the body of a function. If set to NO, these # blocks will be appended to the function's detailed documentation block. # The default value is: NO. HIDE_IN_BODY_DOCS = NO # The INTERNAL_DOCS tag determines if documentation that is typed after a # \internal command is included. If the tag is set to NO then the documentation # will be excluded. Set it to YES to include the internal documentation. # The default value is: NO. INTERNAL_DOCS = NO # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file # names in lower-case letters. If set to YES, upper-case letters are also # allowed. This is useful if you have classes or files whose names only differ # in case and if your file system supports case sensitive file names. Windows # and Mac users are advised to set this option to NO. # The default value is: system dependent. CASE_SENSE_NAMES = NO # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with # their full class and namespace scopes in the documentation. If set to YES, the # scope will be hidden. # The default value is: NO. HIDE_SCOPE_NAMES = NO # If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will # append additional text to a page's title, such as Class Reference. If set to # YES the compound reference will be hidden. # The default value is: NO. HIDE_COMPOUND_REFERENCE= NO # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of # the files that are included by a file in the documentation of that file. # The default value is: YES. SHOW_INCLUDE_FILES = YES # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each # grouped member an include statement to the documentation, telling the reader # which file to include in order to use the member. # The default value is: NO. SHOW_GROUPED_MEMB_INC = NO # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include # files with double quotes in the documentation rather than with sharp brackets. # The default value is: NO. FORCE_LOCAL_INCLUDES = NO # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the # documentation for inline members. # The default value is: YES. INLINE_INFO = YES # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the # (detailed) documentation of file and class members alphabetically by member # name. If set to NO, the members will appear in declaration order. # The default value is: YES. SORT_MEMBER_DOCS = YES # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief # descriptions of file, namespace and class members alphabetically by member # name. If set to NO, the members will appear in declaration order. Note that # this will also influence the order of the classes in the class list. # The default value is: NO. SORT_BRIEF_DOCS = NO # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the # (brief and detailed) documentation of class members so that constructors and # destructors are listed first. If set to NO the constructors will appear in the # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS. # Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief # member documentation. # Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting # detailed member documentation. # The default value is: NO. SORT_MEMBERS_CTORS_1ST = NO # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy # of group names into alphabetical order. If set to NO the group names will # appear in their defined order. # The default value is: NO. SORT_GROUP_NAMES = NO # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by # fully-qualified names, including namespaces. If set to NO, the class list will # be sorted only by class name, not including the namespace part. # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. # Note: This option applies only to the class list, not to the alphabetical # list. # The default value is: NO. SORT_BY_SCOPE_NAME = NO # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper # type resolution of all parameters of a function it will reject a match between # the prototype and the implementation of a member function even if there is # only one candidate or it is obvious which candidate to choose by doing a # simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still # accept a match between prototype and implementation in such cases. # The default value is: NO. STRICT_PROTO_MATCHING = NO # The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo # list. This list is created by putting \todo commands in the documentation. # The default value is: YES. GENERATE_TODOLIST = YES # The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test # list. This list is created by putting \test commands in the documentation. # The default value is: YES. GENERATE_TESTLIST = YES # The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug # list. This list is created by putting \bug commands in the documentation. # The default value is: YES. GENERATE_BUGLIST = YES # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO) # the deprecated list. This list is created by putting \deprecated commands in # the documentation. # The default value is: YES. GENERATE_DEPRECATEDLIST= YES # The ENABLED_SECTIONS tag can be used to enable conditional documentation # sections, marked by \if ... \endif and \cond # ... \endcond blocks. ENABLED_SECTIONS = # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the # initial value of a variable or macro / define can have for it to appear in the # documentation. If the initializer consists of more lines than specified here # it will be hidden. Use a value of 0 to hide initializers completely. The # appearance of the value of individual variables and macros / defines can be # controlled using \showinitializer or \hideinitializer command in the # documentation regardless of this setting. # Minimum value: 0, maximum value: 10000, default value: 30. MAX_INITIALIZER_LINES = 30 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at # the bottom of the documentation of classes and structs. If set to YES, the # list will mention the files that were used to generate the documentation. # The default value is: YES. SHOW_USED_FILES = YES # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This # will remove the Files entry from the Quick Index and from the Folder Tree View # (if specified). # The default value is: YES. SHOW_FILES = YES # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces # page. This will remove the Namespaces entry from the Quick Index and from the # Folder Tree View (if specified). # The default value is: YES. SHOW_NAMESPACES = YES # The FILE_VERSION_FILTER tag can be used to specify a program or script that # doxygen should invoke to get the current version for each file (typically from # the version control system). Doxygen will invoke the program by executing (via # popen()) the command command input-file, where command is the value of the # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided # by doxygen. Whatever the program writes to standard output is used as the file # version. For an example see the documentation. FILE_VERSION_FILTER = # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed # by doxygen. The layout file controls the global structure of the generated # output files in an output format independent way. To create the layout file # that represents doxygen's defaults, run doxygen with the -l option. You can # optionally specify a file name after the option, if omitted DoxygenLayout.xml # will be used as the name of the layout file. # # Note that if you run doxygen from a directory containing a file called # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE # tag is left empty. LAYOUT_FILE = # The CITE_BIB_FILES tag can be used to specify one or more bib files containing # the reference definitions. This must be a list of .bib files. The .bib # extension is automatically appended if omitted. This requires the bibtex tool # to be installed. See also https://en.wikipedia.org/wiki/BibTeX for more info. # For LaTeX the style of the bibliography can be controlled using # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the # search path. See also \cite for info how to create references. CITE_BIB_FILES = #--------------------------------------------------------------------------- # Configuration options related to warning and progress messages #--------------------------------------------------------------------------- # The QUIET tag can be used to turn on/off the messages that are generated to # standard output by doxygen. If QUIET is set to YES this implies that the # messages are off. # The default value is: NO. QUIET = NO # The WARNINGS tag can be used to turn on/off the warning messages that are # generated to standard error (stderr) by doxygen. If WARNINGS is set to YES # this implies that the warnings are on. # # Tip: Turn warnings on while writing the documentation. # The default value is: YES. WARNINGS = YES # If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag # will automatically be disabled. # The default value is: YES. WARN_IF_UNDOCUMENTED = YES # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for # potential errors in the documentation, such as not documenting some parameters # in a documented function, or documenting parameters that don't exist or using # markup commands wrongly. # The default value is: YES. WARN_IF_DOC_ERROR = YES # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that # are documented, but have no documentation for their parameters or return # value. If set to NO, doxygen will only warn about wrong or incomplete # parameter documentation, but not about the absence of documentation. # The default value is: NO. WARN_NO_PARAMDOC = NO # If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when # a warning is encountered. # The default value is: NO. WARN_AS_ERROR = NO # The WARN_FORMAT tag determines the format of the warning messages that doxygen # can produce. The string should contain the $file, $line, and $text tags, which # will be replaced by the file and line number from which the warning originated # and the warning text. Optionally the format may contain $version, which will # be replaced by the version of the file (if it could be obtained via # FILE_VERSION_FILTER) # The default value is: $file:$line: $text. WARN_FORMAT = "$file:$line: $text" # The WARN_LOGFILE tag can be used to specify a file to which warning and error # messages should be written. If left blank the output is written to standard # error (stderr). WARN_LOGFILE = #--------------------------------------------------------------------------- # Configuration options related to the input files #--------------------------------------------------------------------------- # The INPUT tag is used to specify the files and/or directories that contain # documented source files. You may enter file names like myfile.cpp or # directories like /usr/src/myproject. Separate the files or directories with # spaces. See also FILE_PATTERNS and EXTENSION_MAPPING # Note: If this tag is empty the current directory is searched. INPUT = ../include/inja \ ../README.md \ support.md # This tag can be used to specify the character encoding of the source files # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses # libiconv (or the iconv built into libc) for the transcoding. See the libiconv # documentation (see: https://www.gnu.org/software/libiconv/) for the list of # possible encodings. # The default value is: UTF-8. INPUT_ENCODING = UTF-8 # If the value of the INPUT tag contains directories, you can use the # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and # *.h) to filter out the source-files in the directories. # # Note that for custom extensions or not directly supported extensions you also # need to set EXTENSION_MAPPING for the extension otherwise the files are not # read by doxygen. # # If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp, # *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, # *.hh, *.hxx, *.hpp, *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, # *.m, *.markdown, *.md, *.mm, *.dox, *.py, *.pyw, *.f90, *.f95, *.f03, *.f08, # *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf and *.qsf. FILE_PATTERNS = *.c \ *.cc \ *.cxx \ *.cpp \ *.c++ \ *.java \ *.ii \ *.ixx \ *.ipp \ *.i++ \ *.inl \ *.idl \ *.ddl \ *.odl \ *.h \ *.hh \ *.hxx \ *.hpp \ *.h++ \ *.cs \ *.d \ *.php \ *.php4 \ *.php5 \ *.phtml \ *.inc \ *.m \ *.markdown \ *.md \ *.mm \ *.dox \ *.py \ *.pyw \ *.f90 \ *.f95 \ *.f03 \ *.f08 \ *.f \ *.for \ *.tcl \ *.vhd \ *.vhdl \ *.ucf \ *.qsf # The RECURSIVE tag can be used to specify whether or not subdirectories should # be searched for input files as well. # The default value is: NO. RECURSIVE = YES # The EXCLUDE tag can be used to specify files and/or directories that should be # excluded from the INPUT source files. This way you can easily exclude a # subdirectory from a directory tree whose root is specified with the INPUT tag. # # Note that relative paths are relative to the directory from which doxygen is # run. EXCLUDE = # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or # directories that are symbolic links (a Unix file system feature) are excluded # from the input. # The default value is: NO. EXCLUDE_SYMLINKS = NO # If the value of the INPUT tag contains directories, you can use the # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude # certain files from those directories. # # Note that the wildcards are matched against the file with absolute path, so to # exclude all test directories for example use the pattern */test/* EXCLUDE_PATTERNS = # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names # (namespaces, classes, functions, etc.) that should be excluded from the # output. The symbol name can be a fully qualified name, a word, or if the # wildcard * is used, a substring. Examples: ANamespace, AClass, # AClass::ANamespace, ANamespace::*Test # # Note that the wildcards are matched against the file with absolute path, so to # exclude all test directories use the pattern */test/* EXCLUDE_SYMBOLS = stdinja # The EXAMPLE_PATH tag can be used to specify one or more files or directories # that contain example code fragments that are included (see the \include # command). EXAMPLE_PATH = ./examples # If the value of the EXAMPLE_PATH tag contains directories, you can use the # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and # *.h) to filter out the source-files in the directories. If left blank all # files are included. EXAMPLE_PATTERNS = * # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be # searched for input files to be used with the \include or \dontinclude commands # irrespective of the value of the RECURSIVE tag. # The default value is: NO. EXAMPLE_RECURSIVE = YES # The IMAGE_PATH tag can be used to specify one or more files or directories # that contain images that are to be included in the documentation (see the # \image command). IMAGE_PATH = # The INPUT_FILTER tag can be used to specify a program that doxygen should # invoke to filter for each input file. Doxygen will invoke the filter program # by executing (via popen()) the command: # # # # where is the value of the INPUT_FILTER tag, and is the # name of an input file. Doxygen will then use the output that the filter # program writes to standard output. If FILTER_PATTERNS is specified, this tag # will be ignored. # # Note that the filter must not add or remove lines; it is applied before the # code is scanned, but not when the output code is generated. If lines are added # or removed, the anchors will not be placed correctly. # # Note that for custom extensions or not directly supported extensions you also # need to set EXTENSION_MAPPING for the extension otherwise the files are not # properly processed by doxygen. INPUT_FILTER = # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern # basis. Doxygen will compare the file name with each pattern and apply the # filter if there is a match. The filters are a list of the form: pattern=filter # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how # filters are used. If the FILTER_PATTERNS tag is empty or if none of the # patterns match the file name, INPUT_FILTER is applied. # # Note that for custom extensions or not directly supported extensions you also # need to set EXTENSION_MAPPING for the extension otherwise the files are not # properly processed by doxygen. FILTER_PATTERNS = # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using # INPUT_FILTER) will also be used to filter the input files that are used for # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES). # The default value is: NO. FILTER_SOURCE_FILES = NO # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and # it is also possible to disable source filtering for a specific pattern using # *.ext= (so without naming a filter). # This tag requires that the tag FILTER_SOURCE_FILES is set to YES. FILTER_SOURCE_PATTERNS = # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that # is part of the input, its contents will be placed on the main page # (index.html). This can be useful if you have a project on for instance GitHub # and want to reuse the introduction page also for the doxygen output. USE_MDFILE_AS_MAINPAGE = ../README.md #--------------------------------------------------------------------------- # Configuration options related to source browsing #--------------------------------------------------------------------------- # If the SOURCE_BROWSER tag is set to YES then a list of source files will be # generated. Documented entities will be cross-referenced with these sources. # # Note: To get rid of all source code in the generated output, make sure that # also VERBATIM_HEADERS is set to NO. # The default value is: NO. SOURCE_BROWSER = NO # Setting the INLINE_SOURCES tag to YES will include the body of functions, # classes and enums directly into the documentation. # The default value is: NO. INLINE_SOURCES = NO # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any # special comment blocks from generated source code fragments. Normal C, C++ and # Fortran comments will always remain visible. # The default value is: YES. STRIP_CODE_COMMENTS = YES # If the REFERENCED_BY_RELATION tag is set to YES then for each documented # function all documented functions referencing it will be listed. # The default value is: NO. REFERENCED_BY_RELATION = NO # If the REFERENCES_RELATION tag is set to YES then for each documented function # all documented entities called/used by that function will be listed. # The default value is: NO. REFERENCES_RELATION = NO # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set # to YES then the hyperlinks from functions in REFERENCES_RELATION and # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will # link to the documentation. # The default value is: YES. REFERENCES_LINK_SOURCE = YES # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the # source code will show a tooltip with additional information such as prototype, # brief description and links to the definition and documentation. Since this # will make the HTML file larger and loading of large files a bit slower, you # can opt to disable this feature. # The default value is: YES. # This tag requires that the tag SOURCE_BROWSER is set to YES. SOURCE_TOOLTIPS = YES # If the USE_HTAGS tag is set to YES then the references to source code will # point to the HTML generated by the htags(1) tool instead of doxygen built-in # source browser. The htags tool is part of GNU's global source tagging system # (see https://www.gnu.org/software/global/global.html). You will need version # 4.8.6 or higher. # # To use it do the following: # - Install the latest version of global # - Enable SOURCE_BROWSER and USE_HTAGS in the config file # - Make sure the INPUT points to the root of the source tree # - Run doxygen as normal # # Doxygen will invoke htags (and that will in turn invoke gtags), so these # tools must be available from the command line (i.e. in the search path). # # The result: instead of the source browser generated by doxygen, the links to # source code will now point to the output of htags. # The default value is: NO. # This tag requires that the tag SOURCE_BROWSER is set to YES. USE_HTAGS = NO # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a # verbatim copy of the header file for each class for which an include is # specified. Set to NO to disable this. # See also: Section \class. # The default value is: YES. VERBATIM_HEADERS = YES #--------------------------------------------------------------------------- # Configuration options related to the alphabetical class index #--------------------------------------------------------------------------- # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all # compounds will be generated. Enable this if the project contains a lot of # classes, structs, unions or interfaces. # The default value is: YES. ALPHABETICAL_INDEX = YES # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in # which the alphabetical index list will be split. # Minimum value: 1, maximum value: 20, default value: 5. # This tag requires that the tag ALPHABETICAL_INDEX is set to YES. COLS_IN_ALPHA_INDEX = 5 # In case all classes in a project start with a common prefix, all classes will # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag # can be used to specify a prefix (or a list of prefixes) that should be ignored # while generating the index headers. # This tag requires that the tag ALPHABETICAL_INDEX is set to YES. IGNORE_PREFIX = #--------------------------------------------------------------------------- # Configuration options related to the HTML output #--------------------------------------------------------------------------- # If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output # The default value is: YES. GENERATE_HTML = YES # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of # it. # The default directory is: html. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_OUTPUT = html # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each # generated HTML page (for example: .htm, .php, .asp). # The default value is: .html. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_FILE_EXTENSION = .html # The HTML_HEADER tag can be used to specify a user-defined HTML header file for # each generated HTML page. If the tag is left blank doxygen will generate a # standard header. # # To get valid HTML the header file that includes any scripts and style sheets # that doxygen needs, which is dependent on the configuration options used (e.g. # the setting GENERATE_TREEVIEW). It is highly recommended to start with a # default header using # doxygen -w html new_header.html new_footer.html new_stylesheet.css # YourConfigFile # and then modify the file new_header.html. See also section "Doxygen usage" # for information on how to generate the default header that doxygen normally # uses. # Note: The header is subject to change so you typically have to regenerate the # default header when upgrading to a newer version of doxygen. For a description # of the possible markers and block names see the documentation. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_HEADER = # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each # generated HTML page. If the tag is left blank doxygen will generate a standard # footer. See HTML_HEADER for more information on how to generate a default # footer and what special commands can be used inside the footer. See also # section "Doxygen usage" for information on how to generate the default footer # that doxygen normally uses. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_FOOTER = # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style # sheet that is used by each HTML page. It can be used to fine-tune the look of # the HTML output. If left blank doxygen will generate a default style sheet. # See also section "Doxygen usage" for information on how to generate the style # sheet that doxygen normally uses. # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as # it is more robust and this tag (HTML_STYLESHEET) will in the future become # obsolete. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_STYLESHEET = # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined # cascading style sheets that are included after the standard style sheets # created by doxygen. Using this option one can overrule certain style aspects. # This is preferred over using HTML_STYLESHEET since it does not replace the # standard style sheet and is therefore more robust against future updates. # Doxygen will copy the style sheet files to the output directory. # Note: The order of the extra style sheet files is of importance (e.g. the last # style sheet in the list overrules the setting of the previous ones in the # list). For an example see the documentation. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_EXTRA_STYLESHEET = # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or # other source files which should be copied to the HTML output directory. Note # that these files will be copied to the base HTML output directory. Use the # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these # files. In the HTML_STYLESHEET file, use the file name only. Also note that the # files will be copied as-is; there are no commands or markers available. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_EXTRA_FILES = # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen # will adjust the colors in the style sheet and background images according to # this color. Hue is specified as an angle on a colorwheel, see # https://en.wikipedia.org/wiki/Hue for more information. For instance the value # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300 # purple, and 360 is red again. # Minimum value: 0, maximum value: 359, default value: 220. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_COLORSTYLE_HUE = 220 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors # in the HTML output. For a value of 0 the output will use grayscales only. A # value of 255 will produce the most vivid colors. # Minimum value: 0, maximum value: 255, default value: 100. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_COLORSTYLE_SAT = 100 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the # luminance component of the colors in the HTML output. Values below 100 # gradually make the output lighter, whereas values above 100 make the output # darker. The value divided by 100 is the actual gamma applied, so 80 represents # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not # change the gamma. # Minimum value: 40, maximum value: 240, default value: 80. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_COLORSTYLE_GAMMA = 80 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML # page will contain the date and time when the page was generated. Setting this # to YES can help to show when doxygen was last run and thus if the # documentation is up to date. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_TIMESTAMP = NO # If the HTML_DYNAMIC_MENUS tag is set to YES then the generated HTML # documentation will contain a main index with vertical navigation menus that # are dynamically created via Javascript. If disabled, the navigation index will # consists of multiple levels of tabs that are statically embedded in every HTML # page. Disable this option to support browsers that do not have Javascript, # like the Qt help browser. # The default value is: YES. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_DYNAMIC_MENUS = YES # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML # documentation will contain sections that can be hidden and shown after the # page has loaded. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_DYNAMIC_SECTIONS = NO # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries # shown in the various tree structured indices initially; the user can expand # and collapse entries dynamically later on. Doxygen will expand the tree to # such a level that at most the specified number of entries are visible (unless # a fully collapsed tree already exceeds this amount). So setting the number of # entries 1 will produce a full collapsed tree by default. 0 is a special value # representing an infinite number of entries and will result in a full expanded # tree by default. # Minimum value: 0, maximum value: 9999, default value: 100. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_INDEX_NUM_ENTRIES = 100 # If the GENERATE_DOCSET tag is set to YES, additional index files will be # generated that can be used as input for Apple's Xcode 3 integrated development # environment (see: https://developer.apple.com/tools/xcode/), introduced with # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a # Makefile in the HTML output directory. Running make will produce the docset in # that directory and running make install will install the docset in # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at # startup. See https://developer.apple.com/tools/creatingdocsetswithdoxygen.html # for more information. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_DOCSET = NO # This tag determines the name of the docset feed. A documentation feed provides # an umbrella under which multiple documentation sets from a single provider # (such as a company or product suite) can be grouped. # The default value is: Doxygen generated docs. # This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_FEEDNAME = "Doxygen generated docs" # This tag specifies a string that should uniquely identify the documentation # set bundle. This should be a reverse domain-name style string, e.g. # com.mycompany.MyDocSet. Doxygen will append .docset to the name. # The default value is: org.doxygen.Project. # This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_BUNDLE_ID = org.doxygen.Project # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify # the documentation publisher. This should be a reverse domain-name style # string, e.g. com.mycompany.MyDocSet.documentation. # The default value is: org.doxygen.Publisher. # This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_PUBLISHER_ID = org.doxygen.Publisher # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher. # The default value is: Publisher. # This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_PUBLISHER_NAME = Publisher # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three # additional HTML index files: index.hhp, index.hhc, and index.hhk. The # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on # Windows. # # The HTML Help Workshop contains a compiler that can convert all HTML output # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML # files are now used as the Windows 98 help format, and will replace the old # Windows help format (.hlp) on all Windows platforms in the future. Compressed # HTML files also contain an index, a table of contents, and you can search for # words in the documentation. The HTML workshop also contains a viewer for # compressed HTML files. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_HTMLHELP = NO # The CHM_FILE tag can be used to specify the file name of the resulting .chm # file. You can add a path in front of the file if the result should not be # written to the html output directory. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. CHM_FILE = # The HHC_LOCATION tag can be used to specify the location (absolute path # including file name) of the HTML help compiler (hhc.exe). If non-empty, # doxygen will try to run the HTML help compiler on the generated index.hhp. # The file has to be specified with full path. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. HHC_LOCATION = # The GENERATE_CHI flag controls if a separate .chi index file is generated # (YES) or that it should be included in the master .chm file (NO). # The default value is: NO. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. GENERATE_CHI = NO # The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc) # and project file content. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. CHM_INDEX_ENCODING = # The BINARY_TOC flag controls whether a binary table of contents is generated # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it # enables the Previous and Next buttons. # The default value is: NO. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. BINARY_TOC = NO # The TOC_EXPAND flag can be set to YES to add extra items for group members to # the table of contents of the HTML help documentation and to the tree view. # The default value is: NO. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. TOC_EXPAND = NO # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help # (.qch) of the generated HTML documentation. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_QHP = NO # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify # the file name of the resulting .qch file. The path specified is relative to # the HTML output folder. # This tag requires that the tag GENERATE_QHP is set to YES. QCH_FILE = # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help # Project output. For more information please see Qt Help Project / Namespace # (see: http://doc.qt.io/qt-4.8/qthelpproject.html#namespace). # The default value is: org.doxygen.Project. # This tag requires that the tag GENERATE_QHP is set to YES. QHP_NAMESPACE = org.doxygen.Project # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt # Help Project output. For more information please see Qt Help Project / Virtual # Folders (see: http://doc.qt.io/qt-4.8/qthelpproject.html#virtual-folders). # The default value is: doc. # This tag requires that the tag GENERATE_QHP is set to YES. QHP_VIRTUAL_FOLDER = doc # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom # filter to add. For more information please see Qt Help Project / Custom # Filters (see: http://doc.qt.io/qt-4.8/qthelpproject.html#custom-filters). # This tag requires that the tag GENERATE_QHP is set to YES. QHP_CUST_FILTER_NAME = # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the # custom filter to add. For more information please see Qt Help Project / Custom # Filters (see: http://doc.qt.io/qt-4.8/qthelpproject.html#custom-filters). # This tag requires that the tag GENERATE_QHP is set to YES. QHP_CUST_FILTER_ATTRS = # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this # project's filter section matches. Qt Help Project / Filter Attributes (see: # http://doc.qt.io/qt-4.8/qthelpproject.html#filter-attributes). # This tag requires that the tag GENERATE_QHP is set to YES. QHP_SECT_FILTER_ATTRS = # The QHG_LOCATION tag can be used to specify the location of Qt's # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the # generated .qhp file. # This tag requires that the tag GENERATE_QHP is set to YES. QHG_LOCATION = # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be # generated, together with the HTML files, they form an Eclipse help plugin. To # install this plugin and make it available under the help contents menu in # Eclipse, the contents of the directory containing the HTML and XML files needs # to be copied into the plugins directory of eclipse. The name of the directory # within the plugins directory should be the same as the ECLIPSE_DOC_ID value. # After copying Eclipse needs to be restarted before the help appears. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_ECLIPSEHELP = NO # A unique identifier for the Eclipse help plugin. When installing the plugin # the directory name containing the HTML and XML files should also have this # name. Each documentation set should have its own identifier. # The default value is: org.doxygen.Project. # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES. ECLIPSE_DOC_ID = org.doxygen.Project # If you want full control over the layout of the generated HTML pages it might # be necessary to disable the index and replace it with your own. The # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top # of each HTML page. A value of NO enables the index and the value YES disables # it. Since the tabs in the index contain the same information as the navigation # tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. DISABLE_INDEX = NO # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index # structure should be generated to display hierarchical information. If the tag # value is set to YES, a side panel will be generated containing a tree-like # index structure (just like the one that is generated for HTML Help). For this # to work a browser that supports JavaScript, DHTML, CSS and frames is required # (i.e. any modern browser). Windows users are probably better off using the # HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can # further fine-tune the look of the index. As an example, the default style # sheet generated by doxygen has an example that shows how to put an image at # the root of the tree instead of the PROJECT_NAME. Since the tree basically has # the same information as the tab index, you could consider setting # DISABLE_INDEX to YES when enabling this option. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_TREEVIEW = NO # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that # doxygen will group on one line in the generated HTML documentation. # # Note that a value of 0 will completely suppress the enum values from appearing # in the overview section. # Minimum value: 0, maximum value: 20, default value: 4. # This tag requires that the tag GENERATE_HTML is set to YES. ENUM_VALUES_PER_LINE = 4 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used # to set the initial width (in pixels) of the frame in which the tree is shown. # Minimum value: 0, maximum value: 1500, default value: 250. # This tag requires that the tag GENERATE_HTML is set to YES. TREEVIEW_WIDTH = 250 # If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to # external symbols imported via tag files in a separate window. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. EXT_LINKS_IN_WINDOW = NO # Use this tag to change the font size of LaTeX formulas included as images in # the HTML documentation. When you change the font size after a successful # doxygen run you need to manually remove any form_*.png images from the HTML # output directory to force them to be regenerated. # Minimum value: 8, maximum value: 50, default value: 10. # This tag requires that the tag GENERATE_HTML is set to YES. FORMULA_FONTSIZE = 10 # Use the FORMULA_TRANSPARENT tag to determine whether or not the images # generated for formulas are transparent PNGs. Transparent PNGs are not # supported properly for IE 6.0, but are supported on all modern browsers. # # Note that when changing this option you need to delete any form_*.png files in # the HTML output directory before the changes have effect. # The default value is: YES. # This tag requires that the tag GENERATE_HTML is set to YES. FORMULA_TRANSPARENT = YES # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see # https://www.mathjax.org) which uses client side Javascript for the rendering # instead of using pre-rendered bitmaps. Use this if you do not have LaTeX # installed or if you want to formulas look prettier in the HTML output. When # enabled you may also need to install MathJax separately and configure the path # to it using the MATHJAX_RELPATH option. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. USE_MATHJAX = NO # When MathJax is enabled you can set the default output format to be used for # the MathJax output. See the MathJax site (see: # http://docs.mathjax.org/en/latest/output.html) for more details. # Possible values are: HTML-CSS (which is slower, but has the best # compatibility), NativeMML (i.e. MathML) and SVG. # The default value is: HTML-CSS. # This tag requires that the tag USE_MATHJAX is set to YES. MATHJAX_FORMAT = HTML-CSS # When MathJax is enabled you need to specify the location relative to the HTML # output directory using the MATHJAX_RELPATH option. The destination directory # should contain the MathJax.js script. For instance, if the mathjax directory # is located at the same level as the HTML output directory, then # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax # Content Delivery Network so you can quickly see the result without installing # MathJax. However, it is strongly recommended to install a local copy of # MathJax from https://www.mathjax.org before deployment. # The default value is: https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.2/. # This tag requires that the tag USE_MATHJAX is set to YES. MATHJAX_RELPATH = https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.2/ # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax # extension names that should be enabled during MathJax rendering. For example # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols # This tag requires that the tag USE_MATHJAX is set to YES. MATHJAX_EXTENSIONS = # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces # of code that will be used on startup of the MathJax code. See the MathJax site # (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an # example see the documentation. # This tag requires that the tag USE_MATHJAX is set to YES. MATHJAX_CODEFILE = # When the SEARCHENGINE tag is enabled doxygen will generate a search box for # the HTML output. The underlying search engine uses javascript and DHTML and # should work on any modern browser. Note that when using HTML help # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET) # there is already a search function so this one should typically be disabled. # For large projects the javascript based search engine can be slow, then # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to # search using the keyboard; to jump to the search box use + S # (what the is depends on the OS and browser, but it is typically # , /