[ { "path": ".dockerignore", "content": "# binaries\n*.a\n*.so\n*.so.*\n/demo/demo\n\n# NetBeans Project\nnbproject\n\n# IDEA-based IDE project\n.idea/\n\n# VSCode\n.vscode/\n\n# build configuration autogenerated files\n/build\n/output\n*.swp\nCMakeFiles/\nCMakeTmp/\nCMakeCache.txt\nCMakeDoxyfile.in\nCMakeDoxygenDefaults.cmake\ncmake_install.cmake\ninstall_manifest.txt\n_CPack_Packages/\nCPackConfig.cmake\nCPackSourceConfig.cmake\nCTestTestfile.cmake\nTesting/\n/include_public/anjay/anjay_config.h\nposix-config.h\nanjay-*.cmake\nDoxyfile\n/doc/sphinx/source/conf.py\ntools/test-framework-tools/pymbedtls/build/\n\n# other\nMakefile\n*.log\n*.gcda\n*.gcno\n*.gcov\n*~\ntags\n.ycm_extra_conf.py\n.ycm_extra_conf.pyc\n/tests/codegen/*.c\n/tests/codegen/*.cpp\n/tests/integration/build\n__pycache__/\n.gdb_history\n*.orig\n*.egg-info\n*.pyc\n/tools/test-framework-tools/pymbedtls*\ncompile_commands.json\n\n/avs_commons/install\n/doc/sphinx/build\n/doc/sphinx/html\n/doc/doxygen\n/doc/sphinx/source/.doctrees\n!/doc/sphinx/Makefile\n\n# built tutorials\nexamples/build\n" }, { "path": ".github/workflows/anjay-tests.yml", "content": "# Copyright 2017-2026 AVSystem \n# AVSystem Anjay LwM2M SDK\n# All rights reserved.\n#\n# Licensed under AVSystem Anjay LwM2M Client SDK - Non-Commercial License.\n# See the attached LICENSE file for details.\n\nname: Anjay tests\non: [push]\njobs:\n ubuntu2204-compilers-test:\n runs-on: ubuntu-latest\n container: avsystemembedded/anjay-travis:ubuntu-22.04-3.0\n env:\n CC: ${{ matrix.CC }}\n CXX: ${{ matrix.CXX }}\n MEM_CHECK_TOOL: ${{ matrix.MEM_CHECK_TOOL }}\n steps:\n # NOTE: workaround for https://github.com/actions/checkout/issues/760\n - run: git config --global safe.directory '*'\n # NOTE: v2 requires Git 2.18 for submodules, it's not present in the image\n - uses: actions/checkout@v1\n with:\n submodules: recursive\n - run: apt-get update\n - run: apt-get -y install $CC $CXX\n - run: ./devconfig $MEM_CHECK_TOOL --without-analysis -DWITH_VALGRIND_TRACK_ORIGINS=OFF -DWITH_IPV6=OFF\n - run: |\n . /venv/bin/activate\n env CC=gcc LC_ALL=C.UTF-8 make -j\n - run: |\n . /venv/bin/activate\n env CC=gcc LC_ALL=C.UTF-8 make check\n strategy:\n fail-fast: false\n matrix:\n include:\n - CC: gcc-11\n CXX: g++-11\n MEM_CHECK_TOOL: --with-valgrind\n - CC: gcc-12\n CXX: g++-12\n MEM_CHECK_TOOL: --with-valgrind\n - CC: clang-11\n CXX: clang++-11\n MEM_CHECK_TOOL: --with-valgrind\n - CC: clang-12\n CXX: clang++-12\n MEM_CHECK_TOOL: --with-valgrind\n - CC: clang-13\n CXX: clang++-13\n MEM_CHECK_TOOL: --with-valgrind\n - CC: clang-14\n CXX: clang++-14\n MEM_CHECK_TOOL: --without-memcheck # NOTE: workaround for https://bugzilla.mozilla.org/show_bug.cgi?id=1758782\n\n ubuntu2404-compilers-test:\n runs-on: ubuntu-latest\n container: avsystemembedded/anjay-travis:ubuntu-24.04-3.0\n env:\n CC: ${{ matrix.CC }}\n CXX: ${{ matrix.CXX }}\n MEM_CHECK_TOOL: ${{ matrix.MEM_CHECK_TOOL }}\n steps:\n # NOTE: workaround for https://github.com/actions/checkout/issues/760\n - run: git config --global safe.directory '*'\n # NOTE: v2 requires Git 2.18 for submodules, it's not present in the image\n - uses: actions/checkout@v1\n with:\n submodules: recursive\n - run: apt-get update\n - run: apt-get -y install $CC $CXX\n - run: ./devconfig $MEM_CHECK_TOOL --without-analysis -DWITH_VALGRIND_TRACK_ORIGINS=OFF -DWITH_IPV6=OFF\n - run: |\n . /venv/bin/activate\n env CC=gcc LC_ALL=C.UTF-8 make -j\n - run: |\n . /venv/bin/activate\n env CC=gcc LC_ALL=C.UTF-8 make check\n strategy:\n fail-fast: false\n matrix:\n include:\n - CC: gcc-12\n CXX: g++-12\n MEM_CHECK_TOOL: --with-valgrind\n - CC: gcc-13\n CXX: g++-13\n MEM_CHECK_TOOL: --with-valgrind\n - CC: gcc-14\n CXX: g++-14\n MEM_CHECK_TOOL: --with-valgrind\n - CC: clang-17\n CXX: clang++-17\n MEM_CHECK_TOOL: --with-valgrind\n - CC: clang-18\n CXX: clang++-18\n MEM_CHECK_TOOL: --with-valgrind\n - CC: clang-19\n CXX: clang++-19\n MEM_CHECK_TOOL: --with-valgrind\n\n rockylinux9-compilers-test:\n runs-on: ubuntu-latest\n container: avsystemembedded/anjay-travis:rockylinux-9-3.0\n env:\n CC: ${{ matrix.CC }}\n CXX: ${{ matrix.CXX }}\n steps:\n # NOTE: workaround for https://github.com/actions/checkout/issues/760\n - run: git config --global safe.directory '*'\n # NOTE: v2 requires Git 2.18 for submodules, it's not present in the image\n - uses: actions/checkout@v1\n with:\n submodules: recursive\n - run: dnf update -y --nobest\n - run: dnf install -y $CC\n # Solve issues with EPERM when running dumpcap\n - run: setcap '' $(which dumpcap)\n - run: ./devconfig --with-valgrind --without-analysis -DWITH_VALGRIND_TRACK_ORIGINS=OFF -DWITH_IPV6=OFF\n - run: |\n . /venv/bin/activate\n env CC=gcc LC_ALL=C.UTF-8 make -j\n - run: |\n . /venv/bin/activate\n env CC=gcc LC_ALL=C.UTF-8 make check\n strategy:\n fail-fast: false\n matrix:\n include:\n - CC: gcc\n CXX: g++\n - CC: clang\n CXX: clang++\n\n macOS-test:\n runs-on: \"${{ matrix.RUNNER }}\"\n steps:\n # NOTE: v2 requires Git 2.18 for submodules, it's not present in the image\n - uses: actions/checkout@v1\n with:\n submodules: recursive\n - run: brew update\n # NOTE: try the brew install command twice to work around \"brew link\" errors\n - run: INSTALL_CMD=\"brew install python3 openssl\"; $INSTALL_CMD || $INSTALL_CMD\n # NOTE: Some tests don't pass on mbedTLS 3.6.2 now, so we need to install an older version\n # Homebrew only specifiers major version of mbedTLS, so let's pin the version to 3.6.0 manually\n - run: curl -f https://raw.githubusercontent.com/Homebrew/homebrew-core/219dabf6cab172fb8b62b4d8598e016e190c3c20/Formula/m/mbedtls.rb > /tmp/mbedtls.rb\n # HACK: New version of homebrew requires us to install a formulae from a tap, create a tap for our mbedTLS.\n # The change in homebrew is intentional and won't be fixed, for more details see: https://github.com/orgs/Homebrew/discussions/6351\n - run: brew tap-new embedded/mbedtls\n - run: |\n TAP_DIR=\"$(brew --repo embedded/mbedtls)\"\n mkdir -p \"${TAP_DIR}/Formula\"\n cp /tmp/mbedtls.rb \"${TAP_DIR}/Formula/mbedtls.rb\"\n git -C \"${TAP_DIR}\" add Formula/mbedtls.rb\n git -C \"${TAP_DIR}\" -c user.name=\"CI\" -c user.email=\"ci@example.com\" commit -m \"Add custom mbedtls formula\"\n - run: brew install embedded/mbedtls/mbedtls\n - run: brew pin mbedtls\n # NOTE: The above command may have installed a new version of Python, that's why we launch it weirdly\n # NOTE: We manualy create env since devconfig does not use /usr/bin/env python3\n - run: /usr/bin/env python3 -m venv venv\n - run: env JAVA_HOME=\"$JAVA_HOME_17_X64\" ./devconfig --with-asan --without-analysis --no-examples -DWITH_VALGRIND_TRACK_ORIGINS=OFF -DWITH_IPV6=OFF -DMBEDTLS_ROOT_DIR=/opt/homebrew/opt/mbedtls\n - run: |\n . venv/bin/activate\n LC_ALL=en_US.UTF-8 make -j\n - run: |\n . venv/bin/activate\n LC_ALL=en_US.UTF-8 make check\n strategy:\n fail-fast: false\n matrix:\n include:\n - RUNNER: macos-14\n - RUNNER: macos-15\n - RUNNER: macos-26\n" }, { "path": ".github/workflows/coverity.yml", "content": "# Copyright 2017-2026 AVSystem \n# AVSystem Anjay LwM2M SDK\n# All rights reserved.\n#\n# Licensed under AVSystem Anjay LwM2M Client SDK - Non-Commercial License.\n# See the attached LICENSE file for details.\n\nname: Coverity\non:\n push:\n branches: [master]\njobs:\n coverity:\n runs-on: ubuntu-latest\n container: avsystemembedded/anjay-travis:ubuntu-22.04-3.0\n env:\n # NOTE: These need to be configured in GitHub Actions GUI\n COVERITY_EMAIL: ${{ secrets.COVERITY_EMAIL }}\n COVERITY_SCAN_TOKEN: ${{ secrets.COVERITY_SCAN_TOKEN }}\n steps:\n # NOTE: workaround for https://github.com/actions/checkout/issues/760\n - run: git config --global safe.directory '*'\n # NOTE: v2 requires Git 2.18 for submodules, it's not present in the image\n - uses: actions/checkout@v1\n with:\n submodules: recursive\n - run: |\n mkdir -p coverity_tool\n bash -c 'cd coverity_tool && \\\n wget https://scan.coverity.com/download/linux64 --post-data \"token=$COVERITY_SCAN_TOKEN&project=AVSystem%2FAnjay\" -O coverity_tool.tgz && \\\n tar xf coverity_tool.tgz'\n - run: ./devconfig --without-analysis -DWITH_NESTED_FUNCTION_MUTEX_LOCKS=OFF -DWITH_IPV6=OFF\n - run: env LC_ALL=C.UTF-8 ./coverity_tool/cov-analysis*/bin/cov-build --dir cov-int make\n - run: tar zcf cov-int.tgz cov-int\n - run: |\n curl --form \"token=$COVERITY_SCAN_TOKEN\" \\\n --form \"email=$COVERITY_EMAIL\" \\\n --form file=@cov-int.tgz \\\n --form version=$(git rev-parse HEAD) \\\n --form description=\"\" \\\n https://scan.coverity.com/builds?project=AVSystem%2FAnjay\n" }, { "path": ".gitignore", "content": "# binaries\n*.a\n*.so\n*.so.*\n/demo/demo\n\n# NetBeans Project\nnbproject\n\n# IDEA-based IDE project\n.idea/\n\n# VSCode\n.vscode/\n\n# build configuration autogenerated files\n/build\n/coverage\n/output\n*.swp\nCMakeFiles/\nCMakeTmp/\nCMakeCache.txt\nCMakeDoxyfile.in\nCMakeDoxygenDefaults.cmake\ncmake_install.cmake\ninstall_manifest.txt\n_CPack_Packages/\nCPackConfig.cmake\nCPackSourceConfig.cmake\nCTestTestfile.cmake\nTesting/\n/include_public/anjay/anjay_config.h\nposix-config.h\nanjay-*.cmake\nDoxyfile\n/doc/sphinx/source/conf.py\n/doc/sphinx/source_api/api_generated\ntests/integration/run_tests.sh\n\n# other\nMakefile\n*.log\n*.gcda\n*.gcno\n*.gcov\n*~\ntags\n.ycm_extra_conf.py\n.ycm_extra_conf.pyc\n/tests/codegen/*.c\n/tests/codegen/*.cpp\n/tests/integration/build\n__pycache__/\n.gdb_history\n*.orig\n*.egg-info\n*.pyc\n*.cache\ncompile_commands.json\n\n/avs_commons/install\n/doc/sphinx/build\n/doc/sphinx/html\n/doc/doxygen/Doxyfile*\n/doc/sphinx/source/.doctrees\n!/doc/sphinx/Makefile\n\n# built tutorials\nexamples/*-build\n\n# Anjay persistence files\n*-persistence.dat\n\n# Python venv\n/venv/\nbuild/\ndist/\n*.egg-info/\n\n# py-build-cmake cache\n.py-build-cmake_cache\n" }, { "path": ".gitmodules", "content": "[submodule \"deps/avs_commons\"]\n\tpath = deps/avs_commons\n\turl = https://github.com/AVSystem/avs_commons.git\n" }, { "path": "CHANGELOG.md", "content": "# Changelog\n\n## 3.13.1 (April 2nd, 2026)\n\n### Bugfixes\n\n- Tests and documentation corrections\n\n\n## 3.13.0 (March 31st, 2026)\n\n### Features\n- Introduced experimental SSL Error API under `WITH_SSL_ERROR_API` for MbedTLS\n and custom TLS backends\n- Implemented FW Update Object v1.1 Resources.\n- Introduced support for LwM2M 1.2 features:\n - LwM2M CBOR format,\n - Bootstrap Pack operation,\n - Observation Attributes (carried in Observe, not in Write Attributes)\n - `hqmax` and `edge` attributes (`con` attribute is supported separatley from\n LwM2M 1.2, enabled with `ANJAY_WITH_CON_ATTR`),\n - Discover `depth` parameter,\n - SenML-ETCH CBOR & JSON formats for composite operations,\n - deleting Resource Instances.\n\n\n## 3.12.0 (January 30th, 2026)\n\n### BREAKING CHANGES\n\n- PEP 668 was adopted. Using Python based tools requires a virtual environment\n and `devconfig` script ensures it's activated.\n- Most tools from `tests/integration/framework` were extracted\n into `tools/test-framework-tools` directory which is being installed\n in venv by `devconfig`\n\n### Bugfixes\n- Fixed crash in avs_coap when block transfers are disabled and outgoing\n message does not fit into the external output buffer.\n- (commercial version only) Fixed a bug that made it impossible to set a Master\n Secret which length was anything other than 16 bytes (OSCORE).\n- Fixed avs_coap tests for GCC 15\n\n### Features\n- Added traffic interceptor usage to demo application.\n- (commercial version only) Made it possible to set the maximum length of the\n Master Secret and Master Salt using the AVS_COAP_OSCORE_MASTER_SECRET_SIZE\n and AVS_COAP_OSCORE_MASTER_SALT_SIZE options, respectively.\n- Removed experimental tags from server connection status API, IPSO objects v2\n API, Software Management object API, CoAP Download retry API and\n Confirmable Notification status callback API.\n\n### Improvements\n- Reworked the help menu in Anjay Demo.\n- (commercial version only) Added support for running PKCS11 integration tests\n with OpenSSL as (D)TLS backend.\n- Migrated pymbedtls build system to pyproject.toml.\n\n## 3.11.0 (September 26th, 2025)\n\n### BREAKING CHANGES\n\n- Default value of maximal holdoff time during Bootstrap limited from 120 sec.\n to 20 sec. The limit can still be changed using ANJAY_MAX_HOLDOFF_TIME define.\n- If the Server certificate is missing from the Data Model, Anjay falls back to\n PKIX verification, provided that a Trust Store is available, even when the\n certificate usage is set to DANE-TA or DANE-EE.\n- avs_commons 5.5.0 that is used by Anjay 3.11.0 stoped passing the trust store\n to Mbed TLS backend for Certificate Usage 2 or 3. For details on how Anjay\n handles Certificate Usage resource refer to\n Anjay Specification -> Advanced Topics -> Certificate Usage.\n\n### Bugfixes\n\n- Updated avs_commons to a version without a PSK-mode vulnerability in the Mbed\n TLS backend where a client configured for PSK could connect to a server that\n did not know the PSK, due to advertising non-PSK key exchange and skipping\n certificate verification. This issue affected only TLS 1.3 connections with\n Mbed TLS versions ≥ 3.6.1.\n For details, see: https://github.com/AVSystem/avs_commons/releases/tag/5.5.0\n\n### Features\n- (commercial version only) Added support for configuring OSCORE Object for each\n Security Object in Anjay Demo.\n\n## 3.10.0 (May 28th, 2025)\n\n### Features\n- Instruction how to generate packages for Anjay Demo was added to documentation.\n- Dropped support for Ubuntu 18.04 and removed tests for it.\n\n### Bugfixes\n\n- Fixed `devconfig` script which was incorrectly setting Anjay version in logs\n to \"unknown\".\n- Added canceling the Register or Update message exchange if it's in progress\n when Server Disable (with resource execution or by API) is called that could\n have led to disabling the server infinitely.\n\n### Improvements\n\n- Unified script for generating packages in integration tests, now it can also\n be used to generate packages for the Software Management object.\n- The format of the metadata for packages used in integration tests and the\n demo has been revised to be more unambiguous and unified.\n- Added `confirmable_notification_status_cb` handler that is called if\n acknowledgement for confirmable notification is received from the Server or\n some error has occurred.\n\n## 3.9.0 (February 28th, 2025)\n\n### Features\n\n- LwM2M Gateway functionality was added. To see the feature description, API\n documentation and tutorial on its usage, see Anjay docs\n- Added a ``coap_downloader_retry_count`` and ``coap_downloader_retry_delay``\n configuration options that allow to resume the CoAP download process in case\n of network errors.\n\n### Improvements\n\n- Extended the functionality of the flag enabling Connection ID to also include\n connections to the file download CoAP server, in addition to the LwM2M server\n- Migrated GitHub Actions tests on macOS to the macos-14 runner.\n- Refactored test_ghactions.py.\n- Added Github Actions test on macOS for the AppleClang.\n\n### Bugfixes\n\n- Ensured that Github Actions tests on macOS actually runs on LLVM installed\n from Homebrew instead of AppleClang.\n- Minor fix in the devconfig.\n\n## 3.8.1 (November 13th, 2024)\n\n### Improvements\n\n- Improved the coverage script and switched to lcov.\n- In case when the LwM2M server answers with an RST message to a notification\n that is yielding an error value (e.g. failure to read), which effectively\n cancels the notification, Anjay is not infinitely trying to transmit that\n message with error value once again. New behavior is enabled by default, and\n controlled with `WITH_AVS_COAP_OBSERVE_FORCE_CANCEL_ON_UNACKED_ERROR` option\n of `avs_coap`. Existing projects have to opt-in explicitly.\n- Added `--nobest` flag to `dnf update` in Rockylinux image preparation for\n tests to solve installation candidates conflicts.\n\n### Bugfixes\n\n- Actually fixed compatibility with Mbed TLS 3.6.\n- Fixed compatibility of integration test framework with Mbed TLS versions that\n enabled TLS 1.3, but didn't use `MBEDTLS_USE_PSA_CRYPTO`.\n- The -Wformat warning appearing in some compilers has been fixed.\n- Fixed LwM2M CBOR parser incorrectly accepting inputs containing empty arrays\n as keys\n- Prevent from generating non unique session tokens when the monotonic system\n clock granulation is not fine enough.\n- Refactored how timeouts are handled in pymbedtls to be in line with use of\n mbedTLS in avs_commons.\n\n## 3.8.0 (May 28th, 2024)\n\n### BREAKING CHANGES\n\n- Timeout in case of sending a Confirmable Notification does not cancel the\n observation anymore by default.\n\n### Features\n\n- Added a ``connection_error_is_registration_failure`` configuration option that\n allows handling connection errors as Register failures, including the\n automatic retry mechanism\n- Added experimental server connection status API.\n\n### Improvements\n\n- (commercial version only) Changed MSISDN matching method in SMS binding\n feature to allow handling messages with Short Codes as originating number\n\n### Bugfixes\n\n- Fixed a corner case in which a connection error during a non-first Register\n attempt could cause uncontrolled infinite retries\n- Fixed a bug in demo of Advanced Firmware Update module that prevented\n proper handling of security config for targets other than APP\n- Fixed a bug that caused anjay_next_planned_notify_trigger family APIs to\n return an invalid value after canceling observations\n\n## 3.7.0 (February 16th, 2024)\n\n### Features\n\n- Added support for LwM2M 1.2 server object requirement for infinite lifetime\n (lifetime == 0).\n- Introduced @experimental and @deprecated Doxygen tags.\n- Added experimental IPSO objects v2 API.\n- Added experimental Software Management object API.\n\n### Improvements\n\n- Improved integration tests compability and framework stability\n- Added support for wget2 for validating links in documentation (for HTTP/2\n support)\n\n### Bugfixes\n\n- Refactored generation of blockwise Confirmable notifications to avoid a\n possible assertion failure; requests for subsequent blocks of such\n notifications are now sent as Piggybacked responses\n- Fixed a bug in the documentation of an object definition struct\n- (commercial version only) Fixed problems with running some tests on systems\n with Mbed TLS 3.x\n- Fixed a few assertion and pointer punning issues regarding calls to IPSO\n objects APIs in erroneous cases\n- Prevent from trying to store empty cert/keys on HSM\n\n## 3.6.1 (November 21st, 2023)\n\n### Improvements\n\n- Optimized heap memory usage: SenML CBOR payloads for Send and Notify\n operations are no longer serialized in memory in their entirety unless their\n contents depend on the Access Control object state\n- Added a public define for MSISDN string size\n- Optimized \"Out of memory\" logs in favor of a smaller flash memory footprint\n- (commercial feature only) Added API for querying Anjay for SSID associated\n with given MSISDN and SMS Trigger resource value\n\n### Bugfixes\n\n- (commercial feature only) Fixes for various bugs that could cause invalid\n memory accesses when restoring data from corrupted core persistence data\n\n## 3.6.0 (October 9th, 2023)\n\n### Features\n\n- Added APIs for setting custom timeouts for downloads performed over CoAP+TCP\n and HTTP, including firmware update downloads\n- Added `requirements.txt` file to manage Python dependencies more efficiently\n\n### Improvements\n\n- Clarified documentation on behavior of Firmware Update and Advanced Firmware\n Update modules when ``anjay_fw_update_get_security_config_t`` and\n ``anjay_advanced_fw_update_perform_upgrade_t`` callbacks, respectively, are\n not defined.\n- Added compilation flag that disables all composite operations\n\n### Bugfixes\n\n- Updated integration tests so that they pass on macOS\n- Fix abort scenario in Advanced Firmware Update module\n\n## 3.5.0 (September 7th, 2023)\n\n### BREAKING CHANGES\n\n- Reversed the order of calling the ``delivery_handler`` callback vs. canceling\n the observation when sending notifications with 4.xx or 5.xx code; this change\n is breaking only for direct users of ``avs_coap`` API\n\n### Features\n\n- Added APIs for suspending and resuming standalone downloads as well as\n Firmware Update and Advanced Firmware Update PULL-mode downloads\n- Added standalone versions of the Security and Server object implementations,\n that can be customized by the end users\n- Added definitions for common Core Object IDs in the public API\n- Removed potentially faulty assertion in code generated by anjay_codegen.py\n- (commercial feature only) added ``anjay_sim_bootstrap_calculate_md5()``\n function that allows verification whether SIM Bootstrap data has been changed\n (e.g. as a result of SIM OTA)\n\n### Improvements\n\n- Rewritten Send-based reporting in Advanced Firmware Update in such a way that\n it will now work with custom implementations of the Server object\n- Simplified the CoAP downloader implementation so that the\n ``get_remote_hostname`` socket operation is no longer necessary for download\n resumption\n- Made handling of initial peer CSM messages in CoAP+TCP asynchronous\n- Updated the documentation with more descriptive warnings about functions that\n require extra care to maintain thread safety\n- Removed ``const`` qualifier from ``MAKE_URI_PATH()`` compound literal which\n triggers a plausible compiler bug on IAR EWARM v9.30\n- Reading SNI from the Security Object for the FOTA download connection\n\n### Bugfixes\n\n- Fixed a critical bug that caused Anjay to crash when sending notifications\n with 4.xx or 5.xx code over TCP\n- Fixed a regression introduced in 2.13.0 that prevented the Firmware Update\n and Advanced Firmware Update from compiling without the\n ``ANJAY_WITH_DOWNLOADER`` configuration option enabled\n- Fixed a condition where the Register or Update messages could be erroneously\n regenerated when refreshing server connections while already performing a\n Register or Update request\n- Fixed a condition where the connection could be erroneously retried\n automatically when a fatal failure was expected\n- Decoupled the ``WITH_AVS_COAP_TCP`` and ``ANJAY_WITH_LWM2M11`` configuration\n options so that they can be set independently as intended\n- Fixed the ``devconfig`` script and Github Actions configuration for better\n compatibility with building on macOS\n- Refactored TCP binding handling in integration tests for more reliability\n- Fixed the case where CoAP+TCP Abort message could erroneously be sent multiple\n times\n- Loosened some time constraints in Advanced Firmware Update tests\n- Fixed supplemental iid sort in Advanced Firmware Update\n- Fixed too early restart while performing an upgrade using Advanced Firmware\n Update module in Anjay demo app\n- Fixed too early persistence write while performing an upgrade using Advanced\n Firmware Update module in Anjay demo app\n\n## 3.4.1 (June 23rd, 2023)\n\n### Features\n\n- (commercial feature only) New ``sim_bootstrap`` module that implements the\n logic necessary to extract the EF(DODF-bootstrap) file contents from a smart\n card\n\n### Bugfixes\n\n- Fixed a potential crash in case of a specific out-of-memory condition in\n Advanced Firmware Update\n- Fixed `anjay_config_log.h` so that all non-binary configuration options are\n properly logged\n- Fixed a regression from 3.4.0 that prevented ``nsh_lwm2m.py`` from launching\n\n## 3.4.0 (June 14th, 2023)\n\n### Features\n\n- New APIs for server connection lifecycle management:\n ``anjay_server_schedule_reconnect()`` and ``anjay_schedule_register()``\n- New options in ``anjay_configuration_t`` that allow for optional more strict\n LwM2M TS compliance: ``update_immediately_on_dm_change`` and\n ``enable_self_notify``\n- Added option to disable auto-closing of the socket when in queue mode.\n- `avs_coap_observe_cancel()` is now public API (for direct users of avs_coap)\n- Added Advanced Firmware Update as an Anjay module\n- Added simplified demo of Advanced Firmware Update with two firmware images\n- Added tutorial for Advanced Firmware Update\n\n### Improvements\n\n- Observations are now automatically cancelled if the client needs to send a new\n Register messsage\n- Added explicit casts in macros that involve negating an unsigned value, to\n silence warnings generated by some compilers\n- Various improvements and refactors of integration tests, to make them run\n faster and more stable\n- (commercial feature only) Disabled servers are saved now in Core Persistence,\n which prevents them from registering until the timeout passes with respect to\n the real clock.\n\n### Bugfixes\n\n- Fixed handling of SenML payload that could cause erroneous behavior and memory\n leaks when parsing payloads only containing the Base Name field, without Name\n- Fixed error handling in bootstrapper (commercial only) and factory\n provisioning modules so that the changes are properly rolled back in case of\n error\n- Fixed assertion error (or 4.05 Method Not Allowed when compiled without\n assertions) when attempting to set the Disable Timeout resource in the Server\n object when the `ANJAY_WITHOUT_DEREGISTER` configuration option is set\n- Fixed inequality comparisons on some time values that could cause erroneous\n behavior on platforms with low-resolution system clocks, and updated unit\n tests to not assume a high-resolution clock\n- Fixed a problem where `anjay_ongoing_registration_exists()` inconditionally\n returned `true` if any server connection in a \"disabled\" state existed\n- Timeout when sending a Confirmable Notification now cancels the observation,\n as required by RFC 7641\n- Removed sending of Release messages when using CoAP+TCP, which fixes the issue\n of erroneously sending them at the beginning after reconnecting a LwM2M\n connection socket\n- Fixed the serial port handling code in the sample NIDD driver, to properly\n handle cases where more than one line is received in a single read() call\n- Fixed compatibility of integration tests with the current versions of the\n Python cryptography module\n- Fixed problems with compiling the library without `WITH_AVS_COAP_BLOCK`\n enabled (contributed by Flonidan A/S)\n- Fixed a bug in the pymbedtls library used by tests, that prevented it from\n working in DTLS client mode\n- Fixed bug in the \"Custom (D)TLS layers\" code examples\n\n## 3.3.1 (March 10th, 2023)\n\n### Improvements\n\n- `anjay_disable_server()` and `anjay_disable_server_with_timeout()` can now be\n called on servers that are not enabled as well\n\n### Bugfixes\n\n- Fixed resetting of counter for the Communication Sequence Retry Count resource\n- Fixed a regression in 3.2.0 that prevented the bootstrap connection to be\n properly closed if the Bootstrap Server is reconfigured in the new bootstrap\n information and legacy Server-Initiated Bootstrap is disabled\n\n## 3.3.0 (February 21st, 2023)\n\n### Features\n\n- New configuration option, `WITHOUT_MODULE_fw_update_PUSH_MODE` (CMake) / `ANJAY_WITHOUT_MODULE_FW_UPDATE_PUSH_MODE` (header), that allows disabling support for the PUSH mode in the Firmware Update module\n\n### Improvements\n\n- Refactored tests to use `avs_stream_inbuf` instead of `avs_unit_memstream`\n- Refactored `anjay_input_ctx_constructor_t` to use only a single pointer for input stream\n- Revised support for DTLS Connection ID extension, so that a new handshake is\n not performed if Connection ID is used, unless an error occurs\n- Revised example Anjay configurations for embedded builds without CMake to\n optimize compile time and code size\n\n#### Bugfixes\n\n- Fixed a critical regression in 3.2.0 that could cause an assertion failure and use-after-free during Bootstrap Finish if the Bootstrap Server is reconfigured in the new bootstrap information and legacy Server-Initiated Bootstrap is disabled\n- Fixed a bug that could cause undefined behavior when reading the Update Delivery Method resource in the Firmware Update object with thread safety enabled but Downloader disabled\n- Fixed a bug that prevented notifications from being sent in a timely manner after receiving Reset message cancelling an Observation in response to another confirmable notification\n- Fixed a bug that could cause an assertion failure when using `anjay_delete_with_core_persistence()` if a primary server connection failed, but a trigger (SMS) connection is operational\n- Fixed the response code of unsuccessful Resource /1/x/9 Bootstrap-Request Trigger execution (e.g. when there is no Bootstrap-Server Account)\n\n## 3.2.1 (December 13th, 2022)\n\n### Improvements\n\n- Added some missing log messages for potential scheduler errors\n- Updated the version of pybind11 used by integration tests to 2.10.1\n\n### Bugfixes\n\n- Fixed a regression in 3.2.0 that caused some invalid Writes to be silently ignored without responding with proper error codes\n- Fixed compatibility of integration tests with Python 3.11 and the current Github macOS environment\n\n## 3.2.0 (December 7th, 2022)\n\n### BREAKING CHANGES\n\n- Observations are now implicitly canceled when the client's endpoint identity changes (i.e., when the socket is reconnected without a successful DTLS session resumption). This is in line with [RFC 7641](https://datatracker.ietf.org/doc/html/rfc7641#page-22) and LwM2M TS requirements (see [Core 6.4.1](https://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/HTML-Version/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.html#6-4-1-0-641-Observe-Operation) and [Transport 6.4.3](https://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/HTML-Version/OMA-TS-LightweightM2M_Transport-V1_1_1-20190617-A.html#6-4-3-0-643-Registration-Interface)), but **may break compatibility with some non-well-behaved servers.**\n\n### Features\n\n- New APIs to access information about the last registration time, next registration update time and last communication with a server time\n- Expanded `anjay_resource_observation_status_t` structure so that now `anjay_resource_observation_status()` returns also the number of servers that observe the given Resource (capped at newly introduced `ANJAY_MAX_OBSERVATION_SERVERS_REPORTED_NUMBER`) and their SSIDs\n\n### Improvements\n\n- Migrated GitHub Actions tests from Fedora-36 to RockyLinux-9\n- Added compilation flag to enforce Content-Format in Send messages.\n- Refactored Firmware Update notification handling and simplified internal module support\n- Removed the usage of symbolic links between Python packages to make them usable on Windows\n- Key generation in the factory provisioning script has been rewritten to use the cryptography Python module instead of pyOpenSSL\n- Factory provisioning script now uses elliptic curve cryptography by default in certificate mode\n- `anjay_next_planned_lifecycle_operation()` and `anjay_transport_next_planned_lifecycle_operation()` now properly respect jobs that have been scheduled manually (e.g. `anjay_schedule_registration_update()`)\n\n### Bugfixes\n\n- Fixed a bug that could cause some resources in a Write message to be ignored when they follow a Multiple-Instance Resource entry\n- Fixed semantics of Resources 19 and 20 in the Server object, which were mistakenly swapped\n - **NOTE:** The persistence format for the Server object has been reinterpreted so that Resources 19 and 20 remain where they were, without taking semantics into account. This will fix configurations provisioned by Servers but may break configuration persisted just after initially configuring it from code.\n- Made sure that `anjay_schedule_registration_update()` forces a single Update request even when followed by `anjay_transport_schedule_reconnect()` or a change of offline mode\n- Made sure that notifications are not sent before the Update operation if one has been scheduled\n- Made sure that `anjay_transport_schedule_reconnect()` properly reconnects the Bootstrap server connection in all cases\n- Made sure that the socket is properly closed when queue mode is enabled, including previously missing cases related to the Send operation and when no CoAP message needs to be sent at all\n- Refactored asynchronous server connection management to avoid race conditions that could lead to required actions (e.g. EST requests) not being performed when the calculated delays were not big enough\n\n## 3.1.2 (August 24th, 2022)\n\n### Improvements\n\n- Reduced code size of the Security object implementation\n- Updated documentation, readme and examples to mention the new EU IoT Cloud platform\n- Migrated GitHub Actions tests to ubuntu-18.04, ubuntu-20.04, ubuntu-22.04, fedora-36 and macos-11\n\n### Bugfixes\n\n- Fixed various compilation warnings\n- Fixed dangerous usage of `avs_realloc()` in the event loop implementation\n\n## 3.1.1 (July 22nd, 2022)\n\n### Improvements\n\n- Added `CHANGELOG.md`\n\n### Bugfixes\n\n- Added the missing return in anjay_dm_handlers.c that could cause undefined behavior when `ANJAY_WITH_THREAD_SAFETY` was disabled\n- Removed the unused option in the factory provisioning script\n- Removed usage of Python 3.6 syntax in tests that caused Github Actions tests to fail\n- Added missing notes about the change to (D)TLS version in all migration guides in the documentation\n- (commercial feature only) Fixed proper handling of changing the disable_legacy_server_initiated_bootstrap across core persistence cycles\n\n## 3.1.0 (July 6th, 2022)\n\n### BREAKING CHANGES\n\n**Note:** the following changes, while technically breaking, are minor, and should not cause problems in most pratical usages. See also: https://docs.avsystem.com/hubfs/Anjay_Docs/Migrating/MigratingFromAnjay30.html\n\n- Changed error handling semantics of anjay_attr_storage_restore() to match other persistence restore functions\n- TLS 1.2 is no longer implicitly set as the default (D)TLS version; the underlying crypto library's default is now used\n\n### Features\n\n- Factory provisioning feature that allows to perform \"Factory bootstrap\" based on SenML CBOR data stream\n- New API: anjay_access_control_set_owner(), allowing to set Owner resource in the Access Control object during the \"Factory bootstrap\" phase\n- New APIs for changing the CoAP transmission parameters, CoAP exchange timeout and DTLS handshake timeouts while the library is running\n\n### Improvements\n\n- Migrated the Observe/Notify subsystem to use the new AVS_SORTED_SET API from avs_commons; this means that avs_rbtree can be disabled, in which case a more lightweight list-based implementation will be used\n- Minor code size optimizations in the Server object implementation\n- Added documentation for the OSCORE commercial feature\n- (D)TLS version can now be set from command line in the demo application\n\n### Bugfixes\n\n- Fixed a bug in anjay_ongoing_registration_exists() that could cause it to always return true if disable_legacy_server_initiated_bootstrap is set to true\n- Fixed improper formatting of the payload describing the data model in the Register message during initial negotiation of the LwM2M version\n- Fixed handling of persistence format versioning for the Security object, that could cause crashes if Anjay was compiled without LwM2M 1.1 support\n- Changed the \"Bootstrap on Registration Failure\" resource in the Server object to be readable, as specified in LwM2M TS 1.2\n- (commercial feature only) Added persistence of runtime LwM2M version in the core persistence feature; previously the client could erroneously use a different LwM2M version than it registered with after core persistence restore\n\n## 3.0.0 (May 18th, 2022)\n\n### BREAKING CHANGES\n\n- Changed license of the free version to AVSystem-5-clause\n- Refactored the attr_storage module as a core feature\n - Names of the relevant CMake options and configuration macros have changed\n - anjay_attr_storage_install() has been removed; Attribute Storage is now always installed if enabled at compilation time\n - Behavior of anjay_attr_storage_restore() has been changed - this function now fails if supplied source stream is empty\n- The \"con\" attribute is now included in anjay_dm_oi_attributes_t, as it has been standardized for LwM2M TS 1.2\n- Refactored public headers to consistently use conditional compilation; APIs for disabled features are no longer accessible\n- Removed previously deprecated APIs\n- avs_commons 5.0 refactor the API for providing PSK credentials. Please refer to the change log there, or the document below for details: https://docs.avsystem.com/hubfs/Anjay_Docs/Migrating/MigratingFromAnjay215.html\n\n### Features\n\n- LwM2M TS 1.1 support and related features are now available in the open source version; the features include:\n - Support for TCP binding\n - Support for SenML JSON, SenML CBOR and raw CBOR content formats\n - Support for the Send operation\n - Possibility for automatically moving security credentials provisioned by the Bootstrap Server or the bootstrapper module onto hardware security engines (note: no hardware security engine implementation is provided in the open source version)\n- Security credentials provisioned by the Bootstrap server or bootstrapper module and automatically moved onto hardware security engine can now be marked as \"permanent\" to prevent them from being removed\n- (commercial feature only) Experimental support for some LwM2M TS 1.2 features\n\n### Improvements\n\n- Refactored incoming message handling to make use of the `AVS_NET_SOCKET_HAS_BUFFERED_DATA` feature added in avs_commons 5.0\n- Refactored and simplified internal flow of calling data model handlers\n- Refactored internal handling of communication state\n- Commercial features are now available for separate inclusion, described in the documentation more clearly and feature code examples\n- Various improvements in the documentation\n\n## Anjay 2.15.0 (April 8th, 2022)\n\n### Bugfixes\n\n- Fixed some uninitialized variables in IPSO object implementations\n- Fixed some compilation warnings in unit tests\n- Fixed compatibility of integration tests with OpenSSL 3\n- Fixed socket flag handling in tests that were breaking with some versions of Python\n- Fixed some obsolete information in Doxygen documentation\n- (commercial feature only) Added a validity check for the certificate provisioned via EST; previous code could lead to an assertion failure if the server misbehaved or the system clock was not set correctly\n\n### BREAKING CHANGES\n\n- avs_commons 4.10 contains a refator of PSK security credential handling. Please refer to the change log there, or the document below for details: https://docs.avsystem.com/hubfs/Anjay_Docs/Migrating/MigratingFromAnjay214.html\n\n### Features\n\n- Added a new anjay_event_loop_run_with_error_handling() API that automatically restarts the communication in case of a fatal error\n- (commercial version only) Added support for using PSK security credentials located in hardware security engines\n- (commercial version only) Added the possibility for automatically moving security credentials provisioned by the Bootstrap Server or the bootstrapper module onto hardware security engines\n\n### Improvements\n\n- Added proper support for object versioning in the object stub generator\n- Refactored LOG_VALIDATION_FAILED macros in security and server modules to prevent some compilers to generate code with excessive stack usage\n- Stopped using LOG macro in expression context for better compatibility with external logger implementations\n- Added support for Mbed TLS 3.1 in the pymbedtls module used in tests\n\n### Bugfixes\n\n- Fixed firmware update protocol support being erroneously reported when a custom TLS layer is used\n- Changed default \"Minimum Period\" attribute value to 0, as mandated by the specification\n- Fixed a potential memory leak in fw_update module's cleanup routine\n- Fixed the downloader and fw_update modules erroneously passing empty CoAP ETags to the user\n- Fixed ETag handling in the firmware update tutorial examples\n- Fixed handling of objects with names that contain characters that are invalid for C identifiers in the object stub generator\n- Fixed building documentation on newer versions of Sphinx\n- Prevented the custom TLS layer from building during testing if the dependencies are not met\n- (commercial version only) Fixed the wrong resource being written when updating the TLS/DTLS Alert Code resource\n- (commercial version only) Fixed a bug which could cause communication over coaps+tcp to be stalled due to buffering on the TLS layer\n\nAlso updates avs_commons to version 4.10.0. For details, see https://github.com/AVSystem/avs_commons/releases/tag/4.10.0\n\n## Anjay 2.14.1 (November 29th, 2021)\n\n### Features\n\n- added custom TLS layer tutorial,\n- added possibility to generate code for objects with constant number of instances.\n\n### Improvements\n\n- updated avs_commons to version 4.9.1,\n- made avs_coap work with external logger feature,\n- expanded code generation docs.\n\n### Bugfixes\n\n- fixed erronous links in documentation,\n- removed issues from IPSO objects documentation.\n\n## Anjay 2.14.0 (October 1st, 2021)\n\n### Features\n\n- Added anjay_event_loop_run() and anjay_serve_any() APIs that remove the need to implement the event loop manually in client applications\n- Added predefined implementation of some common IPSO object types\n- (commercial version only) Support for PSA API for hardware-based security\n\n### Improvements\n\n- Moved mutex locking from anjay_sched_run() to scheduler jobs themselves, so that custom scheduler jobs are properly supported when thread safety is enabled; this is technically a breaking change against 2.13.0, but the 2.13.0 behaviour has been classified as a defect\n- Refactored the demo client to use the new event loop API\n- Made data types used by anjay_codegen.py more consistent\n- Various improvements and updates to the documentation, including new tutorials about thread safety and the new APIs\n- Improved integration tests so that they are more deterministic\n- Migrated public CI for the open-source version to GitHub Actions\n\n### Bugfixes\n\n- Fixed incorrect behavior of anjay_ongoing_registration_exists() when Server-Initiated Bootstrap was in use (issue #56)\n- Fixed some potential race conditions that could cause anjay_get_socket_entries() to return invalid sockets when downloads were in progress\n- Fixed obsolete URLs in documentation\n\nAlso updates avs_commons to version 4.9.0. For details, see: https://github.com/AVSystem/avs_commons/releases/tag/4.9.0\n\n## Anjay 2.13.0 (July 19th, 2021)\n\n### Features\n\n- Added optional support for thread safety When enabled, all calls to Anjay library functions are protected using built-in mutex, which allows safe integration into multi-threaded applications.\n\n### Improvements\n\n- General improvements when using fw_update module without ANJAY_WITH_DOWNLOADER\n- Add option in demo to provide identity and psk as ASCII string\n\n### Bugfixes\n- Fixed URL in lwm2m_object_registry.py\n- Fix bug in dockerfile with apt-get install change not refreshing apt index\n\nAlso updates avs_commons to version 4.8.1. For details, see: https://github.com/AVSystem/avs_commons/releases/tag/4.8.1\n\n## Anjay 2.12.0 (June 30th, 2021)\n\n### Features\n\n- Added extended log handler implementation, it can be enabled in demo by `--alternative-logger` argument.\n\n### Improvements\n\n- Endpoint name and local MSISDN are copied during anjay_new() along with the rest of the parameters.\n- Demo now checks if binding mode is compatible with the provided URI.\n\n### Bugfixes\n\n- Fixed the case where the LwM2M server requests a block from the middle.\n- Handle fatal CoAP errors during registration, in case of aborted context device will abort registration. (commercial version only)\n\nAlso updates avs_commons to version 4.8.0. For details, see: https://github.com/AVSystem/avs_commons/releases/tag/4.8.0\n\n## Anjay 2.11.1 (June 2nd, 2021)\n\n### Features\n\n- Added anjay_send_batch_data_add_current_multiple_ignore_not_found(), a variant of anjay_send_batch_data_add_current_multiple() that does not treat non-existing resources as an error\n\n### Improvements\n\n- Simplifications in JSON serialization code\n- Relaxed timeout values in some integration tests\n- Added documentation for internal CoAP packet parsing APIs\n- (commercial version only) Read-Composite and Observe-Composite responses now make use of the \"base name\" and \"base time\" SenML labels\n- (commercial version only) Observe response sequence number is now omitted for the TCP transport, as permitted by RFC 8323\n\n### Bugfixes\n\n- Fixed default content-format selection for simple resources if it is not selected by the server and text/plain is disabled at compile time\n- (commercial version only) Fixed a critical bug in anjay_send_batch_data_add_current_multiple() that could cause the batch to be in an inconsistent state if the underlying read operation failed\n- (commercial version only) Fixed a potential memory leak when restoring observation state in anjay_new_from_core_persistence()\n\nAlso updates avs_commons to version 4.7.2. For details, see: https://github.com/AVSystem/avs_commons/releases/tag/4.7.2\n\n## Anjay 2.11.0 (April 29th, 2021)\n\n### Features\n\n- (commercial version only) Added anjay_send_batch_data_add_current_multiple() API for sending multiple resources with the same timestamp\n- (commercial version only) \"send\" command in demo application now supports sending multiple resources at once\n\n### Improvements\n\n- Added documentation for the avs_coap module\n- Added tutorial for using the LwM2M Send method (available in commercial version only)\n- (commercial version only) Resource Instances can now be created through the Write-Composite operation\n- (commercial version only) Made use of Base Name and Base Time labels when generating SenML documents to reduce message size\n\n### Bugfixes\n\n- Enforced decimal base when handling text/plain content format (previously C-style octal and hexadecimal literals were erroneously supported)\n- Made anjay_ongoing_registration_exists() work even if non-default implementation of the Server object is in use\n- Fixed various compilation warnings\n- (commercial version only) Removed erroneous quotes when reporting LwM2M Enabler version in Register requests and Discover responses for LwM2M 1.1\n- (commercial version only) Proper checks for attempts to send data from forbidden objects (Security, OSCORE) via anjay_send_batch_data_add_current()\n- (commercial version only) Added graceful handling of the case when security information provisioned through EST onto an HSM is not accessible, but necessary to attempt bootstrap\n\nAlso updates avs_commons to version 4.7.1. For details, see: https://github.com/AVSystem/avs_commons/releases/tag/4.7.1\n\n## Anjay 2.10.0 (March 19th, 2021)\n\n### Features\n\n- Added additional_tls_config_clb field to anjay_configuration_t that allows for advanced configuration of the TLS backend\n- Added possibility to mix NoSec and secured server connections in demo client\n- Added pretty-printing of JSON payloads in the NSH testing shell\n- (commercial version only) Added APIs to query times of upcoming Register, Update and Notify events\n- (commercial version only) Implemented reporting of Short Server ID for the OSCORE object on Bootstrap-Discover, as required by LwM2M 1.1\n- (commercial version only) Added support for the Trigger resource in the Server object\n- (commercial version only) Added support for the ID Context resource in the OSCORE object\n\n### Improvements\n\n- Refactored _anjay_sync_access_control() to avoid recursion\n- Refactored debug logging of CoAP BLOCK options\n\n### Bugfixes\n\n- Fixed the issue where pmax-based notifications were not being scheduled when Notification Storing was disabled\n- Fixed semantics of the LwM2M Write operation when writing optional resources that are not supported in the implementation; this behaviour has been clarified between LwM2M TS releases 1.1 and 1.1.1\n- Fixed queue-mode server connections superfluously resuming when exiting offline mode if there is no data to be sent\n- Fixed potential NULL dereferences in Security, Server, Access Control and OSCORE object implementations\n- Fixed potential memory leak in data batch storage module (used by Notify and Send operations)\n- More robust state checking in the TLV output module\n- Fixed some linting checks (visibility, header and code duplication verification) that were not executing properly as part of \"make check\" and deduplicated them between subprojects\n- Fixed a bug in pymbedtls module that caused integration tests to sometimes freeze indefinitely\n- Fixed a bug that prevented lwm2m_decode command in the NSH testing shell from working\n- Fixed a problem with building the demo application on Windows\n- (commercial version only) Made LwM2M Send operation work properly when the server connection is suspended due to queue mode operation\n- (commercial version only) Fixed handling of buffer overflow corner cases in the BG96 driver in the demo application\n\nAlso updates avs_commons to version 4.7. For details, see: https://github.com/AVSystem/avs_commons/releases/tag/4.7\n\n## Anjay 2.9.0 (January 18th, 2021)\n\n### BREAKING CHANGES\n\n- Minimum required CMake version is raised to 3.6\n- avs_commons 4.6 contains a refactor of avs_net_local_address_for_target_host() that may be breaking for users who maintain their own socket integration code\n\nFor more detailed information about breaking changes and how your code needs to be updated, see: https://docs.avsystem.com/hubfs/Anjay_Docs/Migrating/MigratingFromAnjay28.html\n\n### Features\n\n- LwM2M Testing Shell is now included in the open-source version, see https://docs.avsystem.com/hubfs/Anjay_Docs/Tools/CliLwM2MServer.html\n- Demo application can now be built even when some of the optional library features (e.g. bootstrap, Access Control, observation support, persistence) are disabled\n- A new guide for writing custom socket integration code, and example lightweight implementation: https://docs.avsystem.com/hubfs/Anjay_Docs/PortingGuideForNonPOSIXPlatforms/NetworkingAPI.html\n\n### Improvements\n\n- Improved wording in migration documentation to make usage clearer\n- Various improvements to integration tests:\n - Tests that involve restarting the demo process now retain execution logs for each launch\n - Fixed a race condition when handling demo process shutdown\n - (commercial version only) Additional tests for rebuilding client certificate chain\n- (commercial version only) CoAP message cache, previously only enabled for UDP, is now also used for SMS and NIDD transports\n- (commercial version only) Made closing NIDD connection in the BG96 driver more resilient to errors\n\n### Bugfixes\n\n- Removed some misleading log messages\n- (commercial version only) Fixed some dependencies between CMake configuration options so that cmake -DDTLS_BACKEND= . works with default settings\n\nAlso updates avs_commons to version 4.6 which, in addition to the breaking change mentioned above, introduces the following changes:\n\n### Improvements\n\n- Additional tests for the avs_stream module\n\nBugfixes\n- Fixed erroneous bounds check in _avs_crypto_get_data_source_definition()\n- Made removal of PKCS#11 objects more resilient to errors (relevant mostly for commercial Anjay users)\n- Fixed CMake code for importing the libp11 library (relevant mostly for commercial Anjay users)\n\n## Anjay 2.8.0 (November 23rd, 2020)\n\n### BREAKING CHANGES\n\nSee below for breaking changes in avs_commons. Note that these are unlikely to affect users that use CMake for building the library, but may require updating configuration headers when using alternative build systems.\n\nFor more detailed information about breaking changes and how your code needs to be updated, see: https://docs.avsystem.com/hubfs/Anjay_Docs/Migrating/MigratingFromAnjay27.html\n\n### Features\n\n- Made use of avs_commons' new floating point formatting functions, making it possible to link against libc implementations that don't support printf(\"%g\")\n- (commercial version only) Support for Enrollment over Secure Transports (EST-coaps) with key and certificate storage on Hardware Security Modules via avs_commons' OpenSSL engine support\n- (commercial version only) Support for certificate chain reconstruction based on trust store when performing (D)TLS handshake - this is especially useful for EST-based security, as certificates provisioned via /est/crts can be used as client certificate chain during handshake\n\n### Improvements\n\n- Better CMake-level dependencies and error handling for compile-time configuration options\n- Fixed various compile-time warnings\n- Included avs_commons and avs_coap configuration in the TRACE-level configuration report log at initialization time\n- Relaxed timeout for Deregister message in integration tests\n- Integration test target logs path is now configurable in runtest.py\n- Various improvements to documentation and examples:\n - Attribute storage module is now installed in most tutorials, making them more complete\n - https://docs.avsystem.com/hubfs/Anjay_Docs/AdvancedTopics/AT-NetworkErrorHandling.html now mentions retry behavior of the commercial version in LwM2M 1.1\n - API documentation generated by Doxygen now properly includes all commercial-only APIs when run in commercial codebase\n - Updated installation instructions for CentOS that referred to non-existent URLs\n - Updated visual style to match corporate identity\n\n### Bugfixes\n\n- Data model persistence routines can no longer be successfully called during the bootstrap procedure, preventing from persisting potentially invalid data\n- Fixed a regression in 2.7.0 that prevented ciphersuite setting from being properly respected for HTTP downloads\n- Fixed a bug that could result in an assertion failure when showing demo client's help message\n- Fixed a bug in \"get_transport\" command implementation in demo client\n- Fixed erroneous setting of AVS_COMMONS_WITH_AVS_CRYPTO_ADVANCED_FEATURES in example configuration headers\n- Removed duplicate file names that could prevent building with some embedded IDEs\n\nAlso updates avs_commons to version 4.5 which introduces the following changes:\n\n### BREAKING CHANGES\n\n- Moved URL handling routines to a separate avs_url component\n- Implementation of avs_net_validate_ip_address() is no longer required when writing custom socket integration layer\n- Hardware Security Module support has been reorganized to allow easier implementation of third-party engines\n\n### Features\n\n- Support for private key generation and removal on Hardware Security Modules via PKCS#11 engine\n- Support for storing and removing certificates stored on Hardware Security Modules via PKCS#11 engine\n- Support for certificate chain reconstruction based on trust store when performing (D)TLS handshake\n- New AVS_DOUBLE_AS_STRING() API and AVS_COMMONS_WITHOUT_FLOAT_FORMAT_SPECIFIERS configuration options, making it possible to stringify floating point numbers on libc implementations that don't support printf(\"%g\")\n\n### Improvements\n\n- Simplified URL hostname validation - it is now somewhat more lenient, but no longer depends on avs_net_validate_ip_address()\n- Removed internal usage of avs_net_validate_ip_address() and reimplemented it as an inline function that wraps avs_net_addrinfo_resolve_ex()\n- Better CMake-level dependencies and compile-time error handling for compile-time configuration options\n- PEM-formatted security objects can now be loaded from buffer in the Mbed TLS backend\n\n### Bugfixes\n\n- Fixed conditional compilation clauses for avs_crypto global initialization\n- Additional NULL checks when loading security information\n- Removed duplicate file names that could prevent building with some embedded IDEs\n\n## Anjay 2.7.0 (October 15th, 2020)\n\n### BREAKING CHANGES\n\n- Changed signature of anjay_security_config_from_dm() and expected lifetime of anjay_security_config_t; removed anjay_fw_update_load_security_from_dm() compatibility alias\n\nNote: For a more detailed information about breaking changes and how your code needs to be updated, see: https://docs.avsystem.com/hubfs/Anjay_Docs/Migrating/MigratingFromAnjay26.html\n\n### Features\n\n- New anjay_download_set_next_block_offset() API that allows skipping parts of downloads\n- (commercial version only) Support for configuring certificate security from external sources during the Factory Bootstrap phase, including initial support for PKCS11-based hardware security\n- (commercial version only) Support for TCP in the NSH testing shell\n\n### Bugfixes\n\n- Fixed support for older versions of Mbed TLS\n- More graceful error handling in anjay_security_object_add_instance()\n- Made the option to disable bootstrap support work again\n- Other bug fixes, partially found using fuzz testing\n\nAlso updates avs_commons to version 4.4 which introduces the following changes:\n\n### BREAKING CHANGES\n\n- Significant refactor of avs_crypto_security_info_union_t family of types (compatibility aliases are available)\n\n### Features\n\n- Initial support for PKCS11-based hardware security\n- New APIs:\n - avs_crypto_certificate_chain_info_array_persistence()\n - avs_crypto_certificate_chain_info_from_engine()\n - avs_crypto_certificate_chain_info_list_persistence()\n - avs_crypto_certificate_chain_info_persist()\n - avs_crypto_cert_revocation_list_info_array_persistence()\n - avs_crypto_cert_revocation_list_info_list_persistence()\n - avs_crypto_cert_revocation_list_info_persist()\n - avs_crypto_private_key_info_copy()\n - avs_crypto_private_key_info_from_engine()\n - avs_crypto_private_key_info_persistence()\n - avs_net_socket_dane_tlsa_array_copy()\n - avs_stream_copy()\n - avs_stream_offset()\n- Added scripts simplifying unit test code coverage calculation\n\n## Anjay 2.6.1 (August 31st, 2020)\n\n### Features\n\n- Added documentation for the LwM2M testing shell (NSH) - note that the shell itself is only available in the commercial version\n\n### Improvements\n\n- Refactored security key loading flow\n\n### Bugfixes\n\n- Fixed testing scripts to make them work on macOS and Raspberry Pi OS again\n- Added __odr_asan to the list of permitted symbols so that \"make check\" succeeds when the library is built with AddressSanitizer enabled\n- (applicable to commercial version only) Fixed a bug in anjay_server_object_set_lifetime() that could lead to sending the Update message twice afterwards\n\nAlso updates avs_commons to version 4.3.1 which introduces the following changes:\n\n### Improvements\n\n- Replaced the test PKCS#7 file in unit tests with a more modern one, that can be loaded properly with newest releases of Mbed TLS\n\n### Bugfixes\n\n- Made the library compile again with Mbed TLS configured without CRL support or without file system support\n- Fixed some testing code to make it work on macOS and Raspberry Pi OS again\n- Added __odr_asan to the list of permitted symbols so that \"make check\" succeeds when the library is built with AddressSanitizer enabled\n\n## Anjay 2.6.0 (August 25th, 2020)\n\n### Features\n\n- Added compile-time option to disable plaintext and TLV format support\n- Added compile-time option to disable usage of the Deregister message\n- Added support for DANE TLSA entries for downloads\n- Added support for Security and Server (and OSCORE in commercial version) persistence to the demo client\n- (commercial version only) More complete support for Enrollment over Secure Transports (EST-coaps), including:\n - Support for /est/sren and /est/crts operations\n - Persistence of EST data\n - Support for application/pkcs7-mime;smime-type=certs-only content format\n- (commercial version only) Implemented OSCORE object persistence\n- (commercial version only) Support for Matching Type and Certificate Usage Resources in the LwM2M Security object\n- (commercial version only) LwM2M Security object Resources that has previously been only supported through Bootstrap Write, are now also exposed through anjay_security_instance_t\n\n### Improvements\n\n- Anjay can now be used on platforms that do not support handling 64-bit integers through printf() and scanf()\n- Stricter command line option parsing in the demo client\n- Improved help message formatting in the demo client\n- (commercial version only) Various improvements to TLV and CBOR handling in the nsh tool\n\n### Bugfixes\n\n- Fixed a bug that could lead to a blocking receive with infinite timeout when DTLS is in use and handshake messages had to be retransmitted\n - NOTE: This, strictly speaking, introduces a BREAKING CHANGE in semantics of `anjay_serve()` and `avs_coap_*_handle_incoming_packet()` - as they no longer wait for the first message to arrive, but handle it in a non-blocking manner. However, this should not matter in practice if recommended patterns of these functions' usage are followed, and in the worst case scenario it may cause poorly written event loop code to behave as a busy loop, but it should not prevent the code from working.\n- Stricter parsing of TLV payloads\n- Fixed calculation of block size when resuming CoAP downloads which did not use the ETag option\n- Made tests related to X.509 certificate mode pass with the OpenSSL backend\n- More graceful error handling in downloader when required callbacks are not passed\n- Fixed various compilation warnings\n- (commercial version only) Fixed a bug that could lead to crash if offline mode was toggled during same-socket CoAP download and another LwM2M exchange was also scheduled\n- (commercial version only) Fixed CMake option dependencies for the EST feature\n\nAlso updates avs_commons to version 4.3 which introduces the following changes:\n\n### Features\n\n- Improved trust store handling, including:\n - Support for configuring usage of system-wide trust store\n - Support for trusted certificate arrays and lists in addition to single entries\n - Support for CRLs\n- Support for DANE TLSA entries\n- Support for loading certs-only PKCS#7 files\n- New avs_crypto_client_cert_expiration_date() API\n- Removed dtls_echo_server tool that has been unused since version 4.1\n\n### Bugfixes\n\n- Fixed a bug that prevented compiling avs_commons without TLS support\n- Fixed missing error handling in avs_persistence_sized_buffer()\n- Fixed a bug in safe_add_int64_t() that could cause a crash if the result of addition was INT64_MIN\n- Fixed various compilation warnings\n\n## Anjay 2.5.0 (July 14th, 2020)\n\n### Features\n\n- Updated AvsCommons to 4.2.1\n- Added new API for etag allocation\n- (commercial version only) Added initial support for Enrollment Over Secure Transport (EST)\n\n### Bugfixes\n\n- Fixed segfault in CoAP downloads caused by cancellation in the middle of the transfer\n- Fixed building tests on CentOS\n- Fixed compilation when WITH_ANJAY_LOGS=OFF is used\n- Fixed handling of transactional LwM2M Write\n- (commercial version only) Fixed download suspension for downloads over shared socket\n\n## Anjay 2.4.4 (July 1st, 2020)\n\n### Features\n\n- Updated avs_commons to version 4.2.0\n- (commercial version) Added API for run-time Lifetime management\n\n### Bugfixes\n\n- (commercial version) Fixed corner case handling of Last Bootstrapped Resource\n\n## Anjay 2.4.3 (June 25th, 2020)\n\n### Improvements\n\n- Added workarounds for non-deterministic operation of time-sensitive integration tests\n\n### Bugfixes\n\n- Fixed a critical bug in error handling of notification sending\n- Fixed some bugs in Docker and Travis integration\n- (commercial version only) Fixed a bug in `anjay_transport_*()` functions that prevented them from working correctly with NIDD transport\n\n## Anjay 2.4.2 (June 17th, 2020)\n\n### Features\n\n- (commercial version only) Implemented NIDD MTU management, allowing to configure maximum message size to be sent, and the maximum message to be received\n- (commercial version only) Added binding mode deduction from URI scheme to demo client\n\n### Improvements\n\n- Added Dockerfile to simplify compiling & launching Anjay demo client on various systems\n- Improved error reporting when executing Registration Update Trigger\n\n### Bugfixes\n\n- Fixed incorrect condition in time_object_notify in tutorials' code\n- Fixed compilation issues of pymbedtls on newer GCC versions\n- Fixed compilation of the demo client on Windows\n\n## Anjay 2.4.1 (May 29th, 2020)\n\n- NOTE: The endpoint name and server URI arguments to the demo client are now mandatory\n\n### Improvements\n\n- Fixed various compilation warnings in certain configurations\n- Updated documentation, readme and examples to mention the new Try Anjay platform\n- Added some missing information in \"Porting guide for non-POSIX platforms\" documentation article\n- Additional script for testing Docker configurations used by Travis locally\n\n### Bugfixes\n\n- Updated avs_commons to version 4.1.3, with more fixes in CMake scripts for corner cases when searching for mbed TLSa, and fix for allowing compilation on platforms that define macros that conflict with avs_log verbosity levels (DEBUG, ERROR etc.)\n- Removed the .clang-format file that relied on features specific to an unpublished custom fork of clang-format\n\n## Anjay 2.4a (May 22nd, 2020)\n\nUpdated avs_commons to version 4.1.2, which fixes interoperability problem with CMake versions older than 3.11.\n\n## Anjay 2.4 (May 21st, 2020)\n\n### Features\n\n- Added anjay_ongoing_registration_exists() API\n- Added anjay_server_get_ssids() API for the default implementation of the Server object\n- Made offline mode configurable independently per transport (UDP, TCP; in commercial version also SMS and NIDD) and respected by downloads (including firmware update)\n- Network integration layer (in commercial version, also SMS and NIDD drivers) may now use avs_errno(AVS_ENODEV) as a special error condition that will NOT trigger connection reset\n- (commercial version only) Added avs_send_deferrable() API\n- (commercial version only) Support for reporting State and Result changes using LwM2M Send messages in the fw_update module\n- (commercial version only) Ability to perform CoAP(S) downloads (including firmware update) over the same socket that is already used for LwM2M communication. In particular, this allows downloads over SMS and NIDD.\n\n### Improvements\n\n- fw_update module now allows reset of the state machine during download\n- Ability to report successful firmware update without reboot through the fw_update module is now officially supported\n- (commercial verison only) OSCORE implementation now properly supports kid_ctx negotiation as specified by RFC 8613 Appendix B.2\n- (commercial version only) Improvements to NIDD handling, to make sure that different packet size limits may be used for incoming and outgoing messages (NOTE: For the commercial version, this includes BREAKING CHANGES)\n\n### Bugfixes\n\n- Made some payload processing errors (including text/plain base64 decoding errors) return 4.00 Bad Request properly instead of 5.00 Internal Server Error\n- The default Disable timeout in the default implementation of the Server object is now 86400 as mandated by the spec instead of infinity\n- (commercial version only) Fixed a bug in timeout handling that sometimes caused the bg96_nidd driver to report spurious errors\n\nAlso updates avs_commons to version 4.1.1, which includes the following changes:\n\n### Bugfixes\n\n- Fixed a bug in CMake scripts that caused link errors when using statically linked versions of mbed TLS\n ## Anjay 2.3a (May 15th, 2020)\n BREAKING CHANGES:\n- Removed usages of the ssize_t type. APIs in both Anjay and avs_commons that had it in public signatures have been redesigned\n- (commercial version only) Retry mechanisms described in LwM2M TS 1.1.1, section 6.2.1.2 are now used by default, which changes the default registration retry policy\n- Updated avs_commons to version 4.1, with the following breaking changes:\n - Renamed public header files for better uniqueness\n - Redesigned socket creation and in-place decoration APIs, including the addition of a requirement to provide PRNG context\n - Renamed some public configuration macros, to unify with the updated compile-time configuration pattern\n - Removed the legacy avs_coap component (the version used by Anjay 1.x)\n - Removed the mbed TLS custom entropy initializer pattern in favor of the new PRNG framework\n\nNote: For a more detailed information about breaking changes and how your code needs to be fixed, see https://docs.avsystem.com/hubfs/Anjay_Docs/Migrating/MigratingFromAnjay225.html\n\n### Features\n\n- Changed project structure, configuration headers and updated build system, so that building the library without using CMake is now officially supported\n- Allowed public access to Anjay's scheduler using anjay_get_scheduler()\n- Code generator now allows omitting some of the resources during generation\n- (commercial version only) Added support for some of the retry mechanisms described in LwM2M TS 1.1.1, including the following resources:\n - Bootstrap on Registration Failure\n - Communication Retry Count\n - Communication Retry Timer\n - Communication Sequence Delay Timer\n - Communication Sequence Retry Count\n- (commercial version only) SMS driver API is now public, allowing for custom driver implementation\n\n### Improvements\n\n- Major overhaul of documentation, including new tutorials for data model and firmware update implementation, as well as guides for migration from both Anjay 1.16 and 2.2\n- Cryptographically secure PRNG is now used whenever possible for generation of CoAP tokens and initial message IDs\n- Improvements to code generator:\n - Refactored the generated code so that programmatic instantiation of Object Instances is now easier\n - Code generated in C++ mode is now more object-oriented and idiomatic\n- Thanks to all compile-time configuration now being accessible via a public header, the demo client can now be compiled even when some optional features are disabled\n- Removed some unused code from the open source version\n\n### Bugfixes\n\n- Fixed a problem that could occur while reconnecting to a server, if the host's local address was switching between IPv4 and IPv6\n- Fixed behavior of anjay_exit_offline() when called immediately after anjay_enter_offline()\n- disable_legacy_server_initiated_bootstrap is now properly respected when reconnecting after a connectivity failure\n- anjay_get_string() and anjay_execute_get_arg_value() now report buffer underruns more reliably\n- Added missing HTTP download timeout logic\n- Errors from the socket's send() method are now properly propagated through the CoAP layer\n- Fixed fatal errors that could occur during some specific CoAP error conditions, including during attempts to silently ignore incoming packets\n- Fixes to minor issues found by Coverity\n- Fixed working on platforms where malloc/calloc returns NULL when 0 bytes is requested\n- Fixed compatibility with some embedded compilers\n- Fixed interoperability with servers that use Uri-Path: '' to represent empty query path, as it seems to be permitted by the CoAP RFC\n- Fixed error codes used by the Portfolio object in the demo client\n- Minor fixes in integration testing framework\n- (commercial version only) Added missing support of LwM2M 1.1-specific resources of the Server object to its persistence functions\n- (commercial version only) Fixed various bugs in the bootstrapper module\n- (commercial version only) Additional verification of NIDD URLs\n- (commercial version only) More robust error handling in demo client's NIDD driver\n\nAlso updates avs_commons to version 4.1, which includes the following changes, in addition to those mentioned above as \"breaking changes\"\n\n\n### Features\n\n- Building without CMake is now officially supported\n- Added idiomatic C++ wrapper for AVS_LIST\n- New API for cryptographically safe PRNGs in avs_crypto\n- File-based streams and default log handler can now be disabled at compile time\n\n### Bugfixes\n\n- Fixed a bug in the default socket implementation that prevented compiling on platforms without the IP_TOS socket option support\n- Fixed improper parsing of empty host in URLs\n- Some previously missed log messages now properly respect WITH_AVS_MICRO_LOGS\n- Fixed a bug in netbuf stream's error handling\n\n## Anjay 2.2.5 (February 7th, 2020)\n\n### Bugfixes\n\n- Updated avs_commons to version 4.0.3, which includes:\n - Fix for scope of avs_net_mbedtls_entropy_init() declaration in deps.h\n - Fix that prevented net_impl.c from compiling when IP_TOS is not available\n\n## Anjay 2.2.4 (January 30th, 2020)\n\n### Bugfixes\n\n- Fixed bugs that caused problems with compilation on macOS and Travis\n- avs_commons 4.0.2 include a fix to TLS backend data loader unit tests\n\n### Features\n\n- Added support for \"micro logs\", removing most of log strings to save space, while retaining all the information useful for debugging\n- avs_commons 4.0.2 include support for proper RFC 6125-compliant validation of certificates against hostnames in the OpenSSL backend\n\n\n## Anjay 2.2.3 (January 17th, 2020)\n\n### Bugfixes\n\n- Fixed error in CoAP message ID assignment when a CoAP request was being sent from a response handler\n\n### Features\n\n- Added anjay_resource_observation_status() API to the open source version\n- Added --server-public-key-file to the demo application\n\n## Anjay 2.2.2 (December 20th, 2019)\n\n### Bugfixes\n\n- Fixed an assertion failure on Cancel Observe arriving while sending a confirmable notification\n\n### Improvements\n\n- Minor workarounds for various compiler warnings\n- Fixed unnecessary building of CoAP library test targets\n\nAlso updates avs_commons to version 4.0.1, which includes the following changes:\n\n### Bugfixes\n\n- Prevented certificate-based ciphersuites from being sent in Client Hello when PSK is used over the OpenSSL backend\n\n### Features\n\n- Introduced \"micro log\" feature and AVS_DISPOSABLE_LOG() macro\n\n## Anjay 2.2.1 (December 6th, 2019)\n\nThis release synchronizes the open-source version of Anjay with the commercial branch, that has been in development since September 2018. Versions 2.0.0 (June 14th, 2019) through 2.2.0 have only been released to commercial customers.\n\nNote that the commercial version includes extensive support for LwM2M TS 1.1 features. These are not available in the open-source version and not described in this changelog.\n\n### BREAKING CHANGES\n\n- Redesigned data model APIs\n - Replaced instance_it and instance_present handlers with list_instances\n - Simplified the instance_create API\n - IIDs for Create are always assigned by Anjay - user code no longer needs to allocate IDs\n - Removed the SSID argument\n - Replaced supported_rids field, resource_present, resource_it and resource_operations handlers with list_resources\n - Redesigned handling of Multiple-Instance Resources:\n - Old APIs for resource arrays are no longer available\n - Read and write handlers now take additional Resource Instance ID argument\n - Removed resource_dim handler\n - Introduced new resource_reset and list_resource_instances handlers\n- Renamed various types, in particular those related to LwM2M Attributes\n- Disallowed 65535 for all levels of IDs, as mandated in LwM2M TS 1.1\n- Changed custom objects in demo client to use Object IDs from the range of Bulk Objects Reserved by AVSystem\n - Additional minor changes to the Test object semantics\n- It is now not possible to build both static and shared versions of Anjay as part of the same build\n- Heavily refactored error handling; some public APIs may require use of avs_error_t instead of plain integer error codes\n- Removed stubs of commercial-only APIs from the open source version\n\n### Features\n\n- Entirely rewritten CoAP implementation\n- Register, Update, Request Bootstrap and confirmable Notify messages are now sent asynchronously and do not block other functionality\n- Notifications in JSON format now include timestamps\n- Added setting to prefer hierarchical Content-Format even when reading simple resources, to improve interoperability with certain server implementations\n- Added support for DTLS Connection ID extension if using a development version of mbed TLS that supports it\n- Added ability to configure (D)TLS ciphersuites\n- Added support for epmin and epmax attributes, specified in LwM2M TS 1.1\n- Moved most of the Access Control mechanism logic from the access_control module (i.e., object implementation) to Anjay core\n- Changed `anjay_execute_get_*()` error codes to ANJAY_ERR constants so that they can be safely propagated by DM handler callbacks\n- Added generating notifications when Access Control object changes\n- New revision of persistent format of the Server object implementation, with redesigned handling of Binding resource\n- Improvements to demo client:\n - Notifications in Device object now work properly in the demo client\n - Demo client now supports different binding modes for different servers\n - Support for more resources in the Cellular Connectivity object\n - Support for Event Log object\n - Support for BinaryAppDataContainer object\n- Added script and build target for finding unused code\n\n### Improvements\n\n- Improvements to logging:\n - Made it easier to compile Anjay without any logs\n - Made some log messages more descriptive\n - Tweaked log levels for better manageability\n- More robust downloader module, including improvements to HTTP ETag handling\n- Allowed Accept option in all incoming requests, for better interoperability with certain server implementations\n- Removed internal scheduler implementation, migrated to avs_sched from avs_commons\n- Made use of stack-allocated avs_persistence contexts\n- Refactored handling of server connections and data in Security and Server objects to be more in line with OMA guidelines\n- Refactored CMake scripts to make use of CMake 3 features\n- Extracted parts of dm_core.c to separate files\n- Improvements to internal symbol naming scheme\n- Simplified a lot of internal APIs, including I/O contexts and DM path handling\n- Various cleanups and improvements of Python-based integration test code\n\n### Bugfixes\n\n- Added missing protocol version in responses to Bootstrap Discover on an object path\n- Various minor bugfixes\n\nAlso updates avs_commons to version 4.0.0, which includes the following changes:\n\n### Breaking changes\n\n- Removed ignoring context feature from avs_persistence\n- Refactored error handling, introducing the new avs_error_t concept\n- Renamed avs_stream_abstract_t to avs_stream_t\n- Renamed avs_net_abstract_socket_t to avs_net_socket_t\n\n### Features\n\n- avs_net\n - Added support for Server Name Identification (D)TLS extension when using OpenSSL, and ability to enable or disable it explicitly\n - Added support for DTLS Connection ID extension if using a development version of mbed TLS that supports it\n - Added possibility to use custom mbed TLS entropy pool configuration\n - Added ability to configure (D)TLS ciphersuites\n - Added propagation of (D)TLS handshake alert codes to user code\n - Implemented accept() call for UDP sockets\n - Added avs_url_parse_lenient function and separate validation functions\n- avs_stream\n - Added avs_stream_membuf_take_ownership function\n - Added avs_stream_membuf_reserve function\n- avs_utils\n - Added avs_unhexlify function\n- avs_algorithm\n - Refactored base64 to support alternate alphabets and padding settings\n- avs_unit\n - Added support for and_then callbacks in mock sockets\n\n### Improvements\n\n- Made logs render \"...\" at the end if truncated\n- Improved compatibility with various platforms, including Zephyr\n- Improved structure of CMake stage configuration, removed unused definitions\n- Reformatted entire codebase\n\n### Bugfixes\n\n- Added extern \"C\" clauses missing in some files, added regression testing for that, fixed some other C++ incompatibilities\n- Fixed some improperly propagated error cases in HTTP client\n- Fixed problems with avs_net sockets not working for localhost if no non-loopback network interfaces are available\n- Fixed some potential NULL dereferences, assertion errors and various other fixes\n\n## Anjay 1.16 (September 12th, 2019)\n\n### Features\n\n- Added anjay_fw_update_set_result API for changing Firmware Update Result at runtime\n\n### Improvements\n\n- Make Travis tests a bit faster by no longer using --track-origins=yes Valgrind argument, and also using pre-built Docker images\n\n### Bugfixes\n\n- Disabled stdin buffering in demo application. Fixes occasional hangs in Python tests\n- Updated usages of deprecated `avs_persistence_*` functions\n- Added mbedx509 to pymbedtls dependencies\n- Fixed issues found by Coverity scan\n\n## Anjay 1.15.5 (April 24th, 2019)\n\n### Bug fixes\n\n- Updated avs_commons to 3.10.0, which includes a fix that drastically (one order of magnitude in some cases) changes the result of `avs_coap_exchange_lifetime()`. Previously the results were not in line with RFC7252 requirements.\n\n### Improvements\n\n- The client will no longer wait indefinitely for Bootstrap Finish, but rather for an interval of at most EXCHANGE_LIFETIME seconds since last Bootstrap Interface operation.\n\n## Anjay 1.15.4 (April 19th, 2019)\n\n### Bugfixes\n\n- Fixed bug that caused Anjay fw_update module `perform_upgrade` handler to be called more than once in some cases\n\n### Improvements\n\n- Anjay CMakeLists.txt does not use `${PROJECT_NAME}` anymore, improving compatibility with projects that include it as sources\n\n## Anjay 1.15.3a (April 5th, 2019)\n\n### Improvements\n\n- Documented retransmission parameters configuration in chapter \"Retransmissions, timeouts & response caching\"\n\n## Anjay 1.15.3 (April 3rd, 2019)\n\n### Bugfixes\n\n- Fixed some issues found by Coverity scan\n- Upgraded avs_commons to version 3.9.1, which includes:\n - Fix of usage of select() on platforms that do not support poll()\n - Added new `AVS_RESCHED_*` APIs\n\n## Anjay 1.15.2 (March 25th, 2019)\n\n### Improvements\n\n- Use https:// URI instead of git:// for avs_commons submodule. This allows fetching the submodule without setting up SSH keys. Fixes [#23](https://github.com/AVSystem/Anjay/issues/23)\n\n## Anjay 1.15.1 (February 19th, 2019)\n\n### Improvements\n\n- Anjay will never attempt to send Register/Update from anjay_delete any more. It used to happen when that message was scheduled to be sent at a time that happened to pass between last anjay_sched_run and anjay_delete calls.\n\n## Anjay 1.15 (February 14th, 2019)\n\n### BREAKING CHANGES\n\n- Updated avs_commons library to 3.9, which extracts an avs_stream_net library to break a dependency cycle between components. Applications that do not use CMake need to manually add libavs_stream_net.a to the linker command line.\n\n### Bugfixes\n\n- PUT/POST requests with an Accept: CoAP option are no longer rejected as invalid.\n- Fixed a bug in HTTPS downloader that caused the download to hang indefinitely if the internal buffer of TLS socket is larger than 4KB and downloaded data length module TLS socket buffer size is larger than 4KB.\n- Aborting HTTP(S) downloads no longer waits for the whole transfer to complete.\n\n## Anjay 1.14.2 (January 29th, 2019)\n\n### Bugfixes\n\n- Fixed NULL pointer dereference in log messages displayed when an unknown attribute with no value is passed to Write-Attributes\n\n## Anjay 1.14.1 (January 22nd, 2019)\n\n### Features\n\n- Added command line flag to the demo client that disables use of stdin\n\n### Improvements\n\n- Removed some code duplicated with avs_commons\n- Fixed some minor issues found by scan-build 7\n- Simplified flow of code for Register, Update and Request Bootstrap operations\n- Reformatted example code\n\n### Bugfixes\n\n- Fixed a bug that prevented attempt to retry DTLS handshake after failed Request Bootstrap operation in some scenarios when Server-Initiated Bootstrap is enabled\n- Fixed misleading, erroneous log message for when receiving CoAP messages time out\n- Fixed the documentation URL test randomly failing on some machines\n\n## Anjay 1.14.0 (December 4th, 2018)\n\n### Improvements\n\n- Added anjay_configuration_t::stored_notification_limit configuration option for limiting the maximum number of notifications stored when the client is offline.\n\n## Anjay 1.13.1 (October 8th, 2018)\n\n### Improvements\n\n- Fixed compilation warnings caused by unused variables / mismatching printf format specifiers\n\n## Anjay 1.13.0 (October 4th, 2018)\n\n### Breaking changes\n\n- anjay_configuration_t::max_icmp_failures field has been removed.\n- Changed the way connection errors are handled. Connections are now NOT automatically retried in most of the cases. Please refer to the documentation (Advanced tutorial -> Network error handling) for a summary of the new semantics.\n\n### Improvements\n\n- Extensive refactor of the server connection handling subsystem.\n- Added timeout for the documentation URL check.\n- Prevented integration tests from running concurrently on Travis.\n\n### Bugfixes\n\n- Fixed behaviour when the attributes are set so that pmax < pmin.\n- Fixed a bug that caused Discover operation on the Security object to erroneously work instead of causing 4.01 Unauthorized error as mandated by the spec.\n- Fixed compilation warnings on various compilers.\n- Upgraded avs_commons to version 3.8.2, which includes:\n - Fixes for proper propagation of avs_stream_close() errors.\n - Fixes for external library dependency checking.\n - Fixes for various compilation warnings.\n - Improved logs from the IP address stringification code.\n\n## Anjay 1.12.1 (September 21st, 2018)\n\nUpdate avs_commons to 3.8.1\n\n## Anjay 1.12.0 (September 21st, 2018)\n\n### Breaking changes\n\n- Updated AvsCommons to 3.8.0, which requires CMake 3.4.0 or higher. This means that Anjay requires CMake 3.4.0 or higher as well.\n- Running tests requires grequests (https://github.com/kennethreitz/grequests) now\n\n### Features\n\n- Allowed configuration of UDP DTLS Handshake transmission parameters by anjay_configuration_t::udp_dtls_hs_tx_params field\n- Allowed configuration of firmware download CoAP transmission parameters by anjay_fw_update_handlers_t::get_coap_tx_params handler implemented by the user\n- Added sequence diagrams for library operations in documentation chapter \"4.4. A few notes on general usage\"\n\n### Improvements\n\n- Reformatted the entire codebase with clang-format\n- Added more tests verifying demo client's behavior in situations with network connectivity issues\n- Explained in the demo application why file descriptors other than 0, 1, 2, are being closed\n\n### Bugfixes\n\n- Fixed the cause of \"could not stringify socket address\" error\n\n## Anjay 1.11.0 (September 4th, 2018)\n\n### Breaking changes\n\n- `Removed ANJAY_BINDING_*` constants. Whenever used, they should now be replaced with plain c-strings, as follows:\n * `ANJAY_BINDING_U` -> `\"U\"`,\n * `ANJAY_BINDING_S` -> `\"S\"`,\n * `ANJAY_BINDING_US` -> `\"US\"`,\n * `ANJAY_BINDING_UQ` -> `\"UQ\"`,\n * `ANJAY_BINDING_SQ` -> `\"SQ\"`,\n * `ANJAY_BINDING_UQS` -> `\"UQS\"`,\n * `ANJAY_BINDING_NONE` -> `\"\"`\n\n### Features\n\n- Implemented anjay_attr_storage_purge(), to allow cleaning up Attribute Storage data without recreating a whole client instance\n- Implemented anjay_access_control_purge(), anjay_access_control_is_modified(), to allow better control over persistence\n- Updated avs_commons to version 3.7.1\n\n### Bugfixes\n\n- Fixed implementation of bytes resources in demo test object code\n- Added missing header in attr_storage.h\n\n### Improvements\n\n- Added support for multiple object versions in lwm2m_object_registry.py script\n- Added some previously missing optional packages to README.md, required to run integration tests\n- Improved performance of integration tests\n- Improved documentation of internal server-related APIs\n- Improved unit tests API, specifically added macros that help building CoAP messages without the knowledge of exact packet encoding\n\n## Anjay 1.10.4 (July 30th, 2018)\n\n### Features\n\n- Added a configuration option that allows disabling Server-Initiated Bootstrap\n\n### Bugfixes\n\n- Very short HTTP downloads now do not hang forever when the server does not close the TCP connection\n\n### Improvements\n\n- Refactored management of bootstrap backoff state\n- Add tests for client behavior after receiving 4.03 Forbidden in response to Register request\n\n## Anjay 1.10.3a (July 19th, 2018)\n\n### Fixes\n\n- Fixed Travis build\n\n## Anjay 1.10.3 (July 19th, 2018)\n\n### Fixes\n\n- Fixed warning about uninitialized retval when compiling in SW4STM32\n\n### Improvements\n\n- Added validation of URLs in documentation\n- Added multiple test cases\n\n## Anjay 1.10.2 (July 10th, 2018)\n\n### Features\n\n- Updated AvsComons to version 3.6.2 which includes:\n * a more restrictive approach to symbols from POSIX or C standard library that should not be used in embedded environments\n * a fix of compilation on ARMCC\n * a fix of compile time warning on IAR\n\n### Fixes\n\n- Fixed client behavior when received a 4.03 Forbidden on LwM2M Register\n- Fixed outdated reference to the LwM2M Specification in the documentation\n\n### Improvements\n\n- Added more tests verifying client behavior in different scenarios\n\n## Anjay 1.10.1 (June 29th, 2018)\n\n### Fixes\n\n- Updated avs_commons to 3.6.1 - fixes compatibility issues in tests.\n\n## Anjay 1.10.0 (June 28th, 2018)\n\n### Features\n\n- Updated avs_commons to 3.6.0, which includes:\n * an abstraction layer over allocator routines, making it possible for the user to provide custom allocation/deallocation functions to be used by AvsCommons,\n * removal of ``AVS_LIST_CONFIG_ALLOC/FREE`` (they are now replaced with calls to ``avs_calloc()`` and ``avs_free()`` respectively),\n * removal of use of all ``time()`` calls,\n * removal of use of variable length array language feature,\n * default socket implementation refactor to use a nonblocking socket API,\n * ``avs_compat_threading`` module, implementing necessary synchronization primitives used across AvsCommons such as mutexes,\n * ``avs_cleanup_global_state()`` method, allowing to (optionally) free any global state implicitly instantiated in AvsCommons,\n * various compatibility fixes for FreeBSD.\n\n- Prevented ``anjay_schedule_reconnect()`` from sending Updates when they are not necessary,\n\n- Introduced an API (``anjay_get_socket_entries()``) allowing to obtain different kinds of sockets used by Anjay.\n\n### Improvements\n\n- Removed all uses of ``malloc()/calloc()/realloc()/free()`` in favor of AvsCommons' memory layer abstraction,\n- Removed all occurrences of ``time()``,\n- Removed all uses of variable length arrays,\n- Improved non-GNU compilers compatibility,\n- Fixed multiple typos in documentation,\n- Fixed LwM2M-level error reporting for some LwM2M requests with unexpected payloads/content-formats (sane error codes are now returned instead of Internal Server Error),\n- Various compatibility fixes for FreeBSD.\n\n### Fixes\n\n- Made bind address family depend on resolved numeric address rather than domain name,\n- Fixed project compilation when ``WITH_AVS_PERSISTENCE`` is disabled.\n\n## Anjay 1.9.3 (May 29th, 2018)\n\n### Improvements\n\n- Updated avs_commons to 3.4.3\n- AVS_ASSERT and AVS_UNREACHABLE macros are now used for assertions that contain string literals. This prevents some compilers from emitting warnings about constant expressions being used in asserts.\n\n## Anjay 1.9.2 (May 28th, 2018)\n\n### Features\n\n- Updated avs_commons to 3.4.2 including various compatibility improvements\n- Added preliminary Windows support\n\n### Bugfixes\n\n- Fixed many different casts between incompatible function types found by gcc 8.1\n- Fixed compile errors caused by some (perfectly valid) CMake option configurations\n\n### Improvements\n\n- Improved documentation of anjay_fw_update_perform_upgrade_t\n- Improved compatibility with compilers without typeof() support\n\n## Anjay 1.9.1 (May 17th, 2018)\n\n### Bugfixes\n\n- Fixed searching for scan-build (\"make analyze\" target) on Ubuntu 18.04\n- Prevented sending superfluous notifications before cleaning up the library\n\nAlso updates avs_commons to version 3.4.1, which includes the following changes:\n\n### Bugfixes\n\n- Fixed bug in avs_http that prevented digest authentication from working\n- Fixed conditional compilation bugs in avs_net that made it impossible to disable certain features\n- Fixed bugs in avs_net unit tests that prevented them from passing on systems without JDK installed and when ran as root\n\n### Improvements\n\n- Simplified TLS session persistence logic (removed dependency on mbed TLS session cache)\n- Fixed compilation warnings on mbed TLS >= 2.7\n- Worked around false positive warnings from scan-build 6.0\n\n## Anjay 1.9.0 (May 11th, 2018)\n\n### Features\n\n* anjay_notify_instances_changed() are now automatically called when manipulating pre-implemented Security and Server objects via module API\n* (commercial version only) Added support for persistence of server registration and notification state, designed for devices with aggressive power saving\n* (commercial version only) Added minimal CoAP file server to the command-line test server application\n\n### Improvements\n\n* BREAKING API CHANGE: Security and Server object implementation modules no longer expose the anjay_dm_object_def_t pointer directly.\n* anjay_schedule_reconnect() now also reconnects downloads started using anjay_download()\n* Notifications with non-success message codes are now always sent as Confirmable messages to ensure consistency with server-side state\n* Integration tests now can be easily launched under rr for easier debugging\n* Added various informative log messages\n* Moved persistence subsystem to avs_commons and migrated to it\n* Fixed various compilation warnings and compatibility with different compilers\n* Major internal codebase refactoring, including:\n * Saner scheduler function signatures\n * Changed registration expiration time to use realtime clock instead of the monotonic one, which improves compatibility with sleep mode scenarios\n * Better hermetization of Observe handling implementation\n * Simplification and better hermetization of server connection handling\n * Reorganization of Registration Interface implementation\n* (commercial version only) More flexible management of commercial features during packaging\n\nAlso updates avs_commons to version 3.4.0, which includes the following changes:\n\n### Features\n\n* Moved persistence subsystem from Anjay and improved upon it:\n * Added support for persisting additional integer types\n * Added support for persisting containers with variable size elements\n * Added ability to check the type of persistence context\n\n### Improvements\n\n* BREAKING API CHANGE: Changed TLS session resumption API so that it is now serialized to and deserialized from user-provided buffer\n* BREAKING API CHANGE: Simplified certificate and key configuration API\n * Note that this change dropped support for some libraries that implement \"fake\" OpenSSL API\n* Refactored avs_log() so that compiler will always parse TRACE-level logs, even if code generation for them is disabled\n* Fixed various compilation warnings and compatibility with different compilers\n* Fixed warnings when compiling with mbed TLS 2.3 and newer\n\n### Bugfixes\n\n* Fixed critical bugs in CoAP option handling:\n * Potential integer overflow\n * Erroneous operation on big-endian machines\n* Added various missing NULL checks\n\n## Anjay 1.8.2 (March 14th, 2018)\n\n### Improvements\n\n- Added X.509 certificate support to pymbedtls Python module.\n- Made `BINDING_MODE_AS_STR` `const`.\n- Changed type of the buffer size argument of `anjay_execute_get_arg_value` to unsigned size_t.\n- Added a note on using LwIP socket integration layer to \"Porting guide for non-POSIX platforms\".\n- Added debug logs in instance validators for Security and Server LwM2M objects.\n- Added proper notifications for \"Last Execute Arguments\" resource of the Test Object in demo client.\n- Disabled Coverity scan on Travis. This avoids marking the build as failing despite all tests passing - Coverity service is \"down for maintenance\" since 2018-02-20, and there seems to be no information on when will it be up again.\n\n### Bugfixes\n\n- Fixed `anjay_schedule_reconnect` behavior when called after the client gives up on reaching a LwM2M server. Previously, only a single reconnection attempt was attempted in such case, regardless of the `max_icmp_failures` configuration option.\n- Fixed compilation errors on compilers that do not support typeof.\n\n## Anjay 1.8.1 (February 28th, 2018)\n\n### Bugfixes\n\n- Fixed infinite loop of Register retransmissions when LwM2M Server ignores Updates and Client attempts to re-register\n- Fixed nested links in README.md\n\n## Anjay 1.8.0 (February 21st, 2018)\n\n### Features\n\n- Added get_security_info() handler to fw_update module, enabling configuration of security information for PULL-mode downloads over encrypted channels\n- Added anjay_fw_update_load_security_from_dm() which allows to match security information from the Security object based on URI\n\n### Bugfixes\n\n- fw_update module will no longer connect to any HTTPS or CoAPS URI without authentication\n\n## Anjay 1.7.3 (February 16th, 2018)\n\n### Features\n\n- anjay_codegen is now able to generate C++ code\n\n### Improvements\n\n- Updated timeouts in integration tests which should improve test result stability\n- Added log when security mode does not match server URI\n\n## Anjay 1.7.2 (February 12th, 2018)\n\n### Bugfixes\n\n- Fix anjay_all_connections_failed(). It is no longer returning true if no LwM2M Servers are configured.\n\n## Anjay 1.7.1 (February 12th, 2018)\n\n### Bugfixes\n\n- Skip retransmission loop in case of DTLS handshake timeout. DTLS packet retransmissions are handled within avs_net_socket_connect anyway, so there is no point in applying yet another exponential backoff loop.\n\n## Anjay 1.7.0 (February 12th, 2018)\n\n### Breaking changes\n\n- Reverted anjay_server_unreachable_handler_t as it has been found that using the handler correctly is close to being impossible.\n\n- Anjay no longer attempts to reach LwM2M Servers indefinitely. Maximum number of retries is now configured via anjay_configuration_t::max_icmp_failures, and by default is set to 7.\n\n### Features\n\n- Introduced anjay_all_connections_failed() method, allowing the user to check if Anjay already gave up on trying to reach LwM2M Servers.\n\n### Improvements\n\n- Downgrade log level in _anjay_dm_foreach_instance() to TRACE.\n\n## Anjay 1.6.1 (January 29th, 2018)\n\n### Features\n\n- Added anjay_server_unreachable_handler_t, that may be implemented by the user to control behavior of Anjay when it failed to connect to the LwM2M Server\n- Added new demo command line option \"--server-unreachable-action\" to be able to present the aforementioned handler in action\n- Added new demo command \"enable-server\" to enable Server of specified SSID\n- Added anjay_disable_server_with_timeout()\n\n### Improvements\n\n- Improved compatibility with CMake 2.8.12\n\n### Bugfixes\n\n- Fixed Update interval: when lifetime is larger than `2*MAX_TRANSMIT_WAIT`, Update is now sent at `lifetime-MAX_TRANSMIT_WAIT` instead of `lifetime/2`\n- Fixed demo command line parsing functions\n- Fixed Travis problems and configuration on CentOS\n\n## Anjay 1.6.0 (January 8th, 2018)\n\n### Breaking changes\n\n- Replaced time_t with int32_t for period Attributes; fixes compatibility with platforms that have unsigned time_t\n\n### Improvements\n\n- Removed useless symlinks that caused problems on Windows\n- Fixed usage of errno constants that are defined by avs_commons compatibility layer; fixes compatibility with platforms that don't declare sane errno constants\n- Improved compatibility with CMake 2.8 and CentOS\n\n### Other\n\n- anjay_persistence_time() is now deprecated\n\n## Anjay 1.5.2 (December 11th, 2017)\n\n### Bugfixes\n\n- Fixed flow of flushing unsent notifications\n- Bug fixes in avs_commons, including:\n - Fixed undefined behavior in CoAP message cache\n - Fixed compatibility with compilers that don't support either stdatomic.h or GCC-style `__sync_*` builtins\n - Prevented CoAP back-off timer randomization from occasionally using negative numbers\n - Fixed minor error handling problems\n - Fixed link commands for TinyDTLS interoperability\n\n### Improvements\n\n- Added WITH_TEST CMake flag\n- Improved compatibility with BSD operating systems\n- Improvements in avs_commons, including:\n - Fixed interoperability with HTTP servers that unexpectedly close connection\n\n## Anjay 1.5.1 (November 27th, 2017)\n\n### Features\n\n- Support HTTP download resumption\n\n### Bugfixes\n\n- Fix some race conditions in integration tests that revealed themselves on slow machines\n- Fix anjay_download() retrying download forever even in case of terminal failures\n- Fix Firmware Update resetting by a null-byte Write\n- Stop scheduling useless LwM2M Updates to the Bootstrap Server\n\n### Improvements\n\n- Test Firmware Update \"not enough storage\" scenario over CoAP\n- Test Firmware Update \"connection lost during download\" scenario over CoAP\n\n## Anjay 1.5.0 (November 20th, 2017)\n\n### Features\n\n- Extracted Firmware Update logic to a separate module so that the end user have to implement device-specific firmware updating logic only\n- Implemented API for firmware update resumption\n- Implemented stub of the portfolio object (in demo client) required for the OMA TestFest 2017\n- Added support for DTLS session resumption as well as register-after-reconnect semantics\n- Added object versioning support\n- Added support for LwM2M Server URIs with Uri-Path and Uri-Query\n\n### Bugfixes\n\n- Fixed travis builds on macOS\n- Fixed a few misleading statements in the documentation\n- Fixed anjay_codegen.py handling of Multiple Instance Resources\n- Fixed Content-Format for responses on Bootstrap Discover request\n- Fixed Write (replace) on Device object instance in demo client\n\n### Improvements\n\n- Added more tests covering OMA TestFest 2017 test cases\n- Allowed configuring Security/Server IIDs from command line in demo\n- Allowed Bootstrap Delete on \"/\"\n- Added support for re-bootstrapping after failed registrations\n- Added anjay_server/security_object_is_modified simiar to anjay_attr_storage_is_modified\n- Updated porting guide\n- Replaced Internal Server Error responses with more specific error codes in a few places\n\n### Other\n\n- Relaxed validator of Update location path, due to specification being unclear (see: https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/230)\n\n## Anjay 1.4.1 (October 16th, 2017)\n\n### Features\n\n- Added CMake option `WITH_STATIC_DEPS_LINKED` that forces direct linkage of the library dependencies into the final target library\n- Migrated to a new time API implemented in avs_commons\n- Removed dependency on wget completely and used built-in downloader instead\n\n### Bugfixes\n\n- Fixed symbol visibility checks\n\n### Improvements\n\n- Renamed a few files to improve compatibility with various IDEs that do not handle files with non-unique naming across the entire project\n- Lowered severity of some log messages that were actually not that critical\n- Published example output from anjay_codegen.py script in the documentation\n\n## Anjay 1.4.0 (September 8th, 2017)\n\n### Features\n\n- New tools: lwm2m_object_registry.py and anjay_codegen.py, that allow automatic generation of object implementation stubs from LwM2M object definition XMLs\n- anjay_download() now supports HTTP(S), using the client from avs_commons\n- New APIs for querying Anjay's network traffic statistics\n- New APIs in attr_storage for direct attribute manipulation:\n - anjay_attr_storage_set_object_attrs()\n - anjay_attr_storage_set_instance_attrs()\n - anjay_attr_storage_set_resource_attrs()\n- CoAP implementation base has been refactored and moved to avs_commons, so that it can now be used standalone; Anjay code has been refactored accordingly\n\n### Bugfixes\n\n- Fixed a bug that prevented anjay_get_string() from working as documented when the buffer was too short\n- Fixed conformance with RFC 7252 when sending error responses on observed resources (previously the Observe header was erroneously included)\n- Fixed various minor bugs found through static code analysis and compilation on various platforms\n\n### Improvements\n\n- POSIX dependencies are now better isolated to ease porting onto non-POSIX platforms\n- Added more documentation, including:\n - New tutorial page (BT4) with general notes on library usage\n - Porting guide for non-POSIX platforms\n- Removed some superfluous log messages\n\n## Anjay 1.3.3 (July 27th, 2017)\n\n### Features\n\n- Implemented anjay_download() API for asynchronous CoAP(S) downloads\n- Added anjay_download example code\n- Added support for CoAP firmware download in demo application\n\n### Bugfixes\n\n- Fixed Register/Update transport when changing Binding\n- Fixed lt/gt/st semantics according to https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/191\n- Fixed handling of unrelated BLOCK2 requests during a block-wise Read\n- Disallowed Write-Attributes requests if the server does not have Read access rights\n- Fixed build instructions for OS X in README\n\n### Improvements\n\n- Added packet capture in Python tests\n- Added compilation instructions for Android\n- Made missing scan-build a fatal error if static analysis was enabled with a CMake flag\n- Integrated Coverity scan with Travis build\n- Allowed configuration of CoAP transmission parameters in anjay_new()\n\n## Anjay 1.3.2 (July 13th, 2017)\n\n### Features\n\n- Added custom Attribute \"con\" that may be used to enforce sending Confirmable Notifications for observed entities.\n\n- Added new chapter of the Tutorial about Executable Resources.\n\n- Added documentation subsection about relation LwM2M Discover and Attribute Storage.\n\n### Improvements\n\n- Removed dependency to Boost.Python in tests, and migrated to pybind11 instead (included as a submodule).\n\n- Implemented sending Update after Lifetime Resource has changed (https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/185)\n\n- Implemented proper Bootstrap Server Account purge logic (https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/195)\n\n- Improved handling of CoAP Ping messages - they no longer produce error messages in the logs.\n\n- Documented `ANJAY_ERR_*` constants.\n\n- Added more NULL-assertions in the example demo client.\n\n- Enabled scan-build in make check by default.\n\n- Bumped all copyright years.\n\n### Bugfixes\n\n- Fixed dead URLs in the documentation.\n\n- Fixed segfault when Bootstrap Discover was performed on a non-existing Object.\n\n- Fixed various minor issues found by the static analysis tools.\n\n- Fixed various compilation issues when compiled on older Android platforms.\n\n## Anjay 1.3.1 (June 22nd, 2017)\n\n### Features\n\n- Added `confirmable_notifications` field to `anjay_configuration_t`, enabling the client to only send LwM2M Notify as CoAP Confirmable messages.\n- Added retransmission detection using message cache with fixed size, configurable at library initialization.\n- Added Custom Object/Notifications tutorial with example client.\n- Added documentation page explaining message cache purpose and usage.\n\n### Improvements\n\n- Added support for Write on Instance with superfluous TLV instance header. Anjay used to reject such requests as malformed.\n- Implemented ETS test 204 (Read with Accept: JSON).\n- Made attribute parsing stricter. Unknown or duplicate attributes now cause Bad Request responses\n- Splitted `anjay.h` header into smaller ones. Note: `anjay.h` now includes all other headers, so no changes to user code are required.\n\n### Bugfixes\n\n- Fixed problem with duplicate request aborting block-wise Read responses.\n- Prevented tests from failing if Sphinx is not installed.\n- Fixed ConnectivityMonitoring.APN type to Multiple Resource. Fixes issue #10.\n- Fixed semantics of `lt` and `gt` attributes to match draft-ietf-core-dynlink document.\n- Fixed build issue when configuring build with -DWITH_BOOTSTRAP=OFF CMake option.\n- Fixed compilation warnings in relase builds.\n\n## Anjay 1.3.0 (May 26th, 2017)\n\n### Features\n\n* Added initial output-only support for JSON Content-Format\n* Added support for SMS-related Resources in security module\n* Refactored code to facilitate support for SMS Binding\n * Actual SMS Binding support now implemented in the commercial version\n\n### Improvements\n\n* BREAKING API CHANGE: Replaced rid_bound and resource_supported handler with statically declared list of supported resources\n* Improved handling of DTLS backends in build system\n* 5.03 Service Unavailable is now sent instead of Reset when an unexpected request arrives while waiting for a response to Register or Update\n* Improvements in demo client:\n * Fixed Firmware Update object state machine\n * Added default Access Control entries\n\n### Bugfixes\n\n* Fixed sending errnoeus 2.31 Continue if the last block payload chunk trigerred an error\n* Relaxed invariants for Client-Initiated Bootstrap as per https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/164\n* Prevented sending Object Instance list in Update messages if only changes are in the Security object\n* Fixed various bugs in access_control module\n\n### Other\n\n* Fixed in-code version numbers\n\n## Anjay 1.2.1 (April 10th, 2017)\n\n### Features\n\n* Added automatic Update after object (de)register\n\n### Bugfix\n\n* Fixed potential access violation in anjay_attr_storage_restore()\n\n## Anjay 1.2.0 (April 3rd, 2017)\n\n### Features\n\n* Added new API: anjay_unregister_object()\n\n### Improvements\n\n* Added new constant: ANJAY_ERR_SERVICE_UNAVAILABLE\n* Made documentation linter work better when the MD5 file is broken\n* Refactored anjay_dm_object_def_t, introduced anjay_dm_handlers_t\n* Refactored attr_storage so that object wrapping is no longer necessary\n* Fixed Travis configuration and added macOS build\n* Refactored access_control implementation, simplified API\n* Removed the on_register object handler\n\n## Anjay 1.1.1 (March 14th, 2017)\n\n### Features\n\n* Added API to specify configuration for CoAP sockets, including overriding path MTU\n* Added support for new DTLS backend: tinydtls\n\n### Improvements\n\n* When CoAP logic is blocked on BLOCK processing, 5.03 is now sent as response to unrelated requests\n* Anjay can now be compiled and run on macOS\n* Updated compliance to the released 1.0 specification\n* Added actual reconnection of sockets when using queue mode\n\n### Bugfixes\n\n* Fixes to various issues found using static analysis\n* Fixed compliance issues with handling Bootstrap-Server Account Timeout\n* Removed automatic instantiation of Access Control object instances, as per https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/192\n* Fixed handling of integration test dependencies in CMake files\n* Workaroud for bug in mbed TLS, see https://github.com/Mbed-TLS/mbedtls/issues/843\n\n## Anjay 1.1.0 (February 22nd, 2017)\n\n### Features\n\n* Demo client loads certificates from files\n* Added Bootstrap Awareness tutorial\n* Added Access Control tutorial\n* Added DTLS tutorial\n* Refactored Attribute handling to meet current LwM2M standard requirements\n* Improved out of source build support\n* Improved test coverage\n\n### Bugfixes\n\n* Fixed coverage script\n* Fixed fuzz tests compilation & running on some configurations\n* Fixed mbedTLS detection in integration tests\n* Fixed a case where mismatched Resource ID was accepted in the TLV payload\n* Fixed compilation of tests under gcc-4.6\n* Fixed detection of the required python version\n\n### Other\n\n* Added missing license headers\n* Lowered loglevel of some less important messages\n* Refactored some of the macros and replaced them with real C code\n* Replaced all \"LWM2M\" with \"LwM2M\"\n* Other minor fixes\n\n## Anjay 1.0.0 (February 8th, 2017)\n\nInitial release.\n" }, { "path": "CMakeLists.txt", "content": "# Copyright 2017-2026 AVSystem \n# AVSystem Anjay LwM2M SDK\n# All rights reserved.\n#\n# Licensed under AVSystem Anjay LwM2M Client SDK - Non-Commercial License.\n# See the attached LICENSE file for details.\n\ncmake_minimum_required(VERSION 3.16)\n\nproject(anjay C)\nset(ANJAY_VERSION \"23f4cd115\" CACHE STRING \"Anjay library version\")\nset(ANJAY_BINARY_VERSION 1.0.0)\n\nset(ANJAY_SOURCE_DIR \"${CMAKE_CURRENT_SOURCE_DIR}\")\nset(ANJAY_BUILD_OUTPUT_DIR \"${CMAKE_CURRENT_BINARY_DIR}/output\")\nset(CMAKE_RUNTIME_OUTPUT_DIRECTORY \"${ANJAY_BUILD_OUTPUT_DIR}/bin\")\nset(CMAKE_LIBRARY_OUTPUT_DIRECTORY \"${ANJAY_BUILD_OUTPUT_DIR}/lib\")\nset(CMAKE_ARCHIVE_OUTPUT_DIRECTORY \"${ANJAY_BUILD_OUTPUT_DIR}/lib\")\n\nset(CMAKE_USE_RELATIVE_PATHS TRUE)\nset(CMAKE_EXPORT_COMPILE_COMMANDS ON)\n\ninclude(CheckFunctionExists)\n\nif(WITH_DEMO OR WITH_INTEGRATION_TESTS)\n # ensure Python venv is active\n include(cmake/requirePython3venv.cmake)\nendif()\n\n# On Linux, one needs to link libdl to use dlsym(). On BSD, it is not necessary,\n# and even harmful, since libdl does not exist.\nset(CMAKE_REQUIRED_INCLUDES \"dlfcn.h\")\nforeach(lib \"\" dl)\n message(STATUS \"Looking for dlsym() in library: ${lib}\")\n set(CMAKE_REQUIRED_LIBRARIES ${lib})\n\n # check_function_exists caches its result; make sure the check is\n # actually repeated for each lib\n unset(HAVE_DLSYM CACHE)\n check_function_exists(dlsym HAVE_DLSYM)\n set(CMAKE_REQUIRED_LIBRARIES)\n\n if(HAVE_DLSYM)\n set(DETECTED_DLSYM_LIBRARY \"${lib}\" CACHE STRING \"\" FORCE)\n break()\n endif()\nendforeach()\nset(CMAKE_REQUIRED_INCLUDES)\nset(DLSYM_LIBRARY \"${DETECTED_DLSYM_LIBRARY}\" CACHE STRING \"Name of the library containing dlsym() symbol\")\n\ninclude(CMakeDependentOption)\n\n# compilation flags\nset(CMAKE_C_STANDARD 99)\nset(CMAKE_C_EXTENSIONS OFF)\n\noption(WITH_EXTRA_WARNINGS \"Enable extra compilation warnings\" OFF)\nif(WITH_EXTRA_WARNINGS)\n set(CMAKE_C_FLAGS \"${CMAKE_C_FLAGS} -pedantic -Wall -Wextra -Winit-self -Wmissing-declarations -Wc++-compat -Wsign-conversion -Wconversion -Wcast-qual -Wvla -Wno-variadic-macros -Wno-long-long -Wshadow\")\n if(CMAKE_C_COMPILER_ID MATCHES \"GNU\")\n set(CMAKE_C_FLAGS \"${CMAKE_C_FLAGS} -Wjump-misses-init\")\n endif()\nendif()\n\ninclude(${CMAKE_CURRENT_LIST_DIR}/deps/avs_commons/cmake/PosixFeatures.cmake)\n\noption(WITH_LIBRARY_SHARED \"Compile Anjay as shared library\" \"${UNIX}\")\nif(WITH_LIBRARY_SHARED)\n # It is not possible to create a shared library if -fPIC is not enabled for\n # either Anjay or any of its dependencies.\n set(CMAKE_POSITION_INDEPENDENT_CODE ON)\nendif()\n\n################# TUNABLES #####################################################\n\nset(MAX_PK_OR_IDENTITY_SIZE 2048 CACHE STRING\n \"Maximum supported size (in bytes) of 'PK or Identity' Resource in Security object.\")\nset(MAX_SECRET_KEY_SIZE 256 CACHE STRING\n \"Maximum supported size (in bytes) of 'Secret Key' Resource in Security object.\")\n\n# Following options refer to the payload of plaintext-encoded CoAP packets.\nset(MAX_DOUBLE_STRING_SIZE 512 CACHE STRING\n \"Maximum supported length (in characters) of a string that can be parsed as a double-precision float value, including trailing nullbyte.\")\n\n# CoAP guarantees that Uri-Path/Uri-Query/Location-Path/Location-Query option\n# values are at most 255 characters long, so default values will work for all\n# CoAP requests. Reducing these values is discouraged.\nset(MAX_URI_SEGMENT_SIZE 256 CACHE STRING\n \"Maximum supported length (in characters) of a single Uri-Path/Location-Path CoAP option value, including trailing nullbyte.\")\nset(MAX_URI_QUERY_SEGMENT_SIZE 256 CACHE STRING\n \"Maximum supported length (in characters) of a single Uri-Query CoAP option value, including trailing nullbyte.\")\n\nset(DTLS_SESSION_BUFFER_SIZE 1024 CACHE STRING\n \"Size of the buffer that caches DTLS session information for resumption support.\")\n\nset(MAX_OBSERVATION_SERVERS_REPORTED_NUMBER 0 CACHE STRING\n \"Maximum number of servers observing a given Resource listed by anjay_resource_observation_status() function.\")\n\nset(ANJAY_DEFAULT_SEND_FORMAT AVS_COAP_FORMAT_NONE CACHE STRING\n \"Default value of Content-Format used in Send messages. Value AVS_COAP_FORMAT_NONE(65535) means no default value.\")\n\nset(MAX_HOLDOFF_TIME 20 CACHE STRING\n \"Upper limit for the Hold Off Time for the Bootstrap connection.\")\n\n################# FEATURES THAT REQUIRE LIBRARY CONFIGURATION ##################\n\noption(WITH_AVS_PERSISTENCE \"Enable support for persisting objects data\" ON)\n\noption(WITH_BOOTSTRAP \"Enable LwM2M Bootstrap Interface support\" ON)\noption(WITHOUT_TLV \"Disable support for TLV content format\" OFF)\noption(WITH_DOWNLOADER \"Enable support for downloader API\" ON)\ncmake_dependent_option(WITH_HTTP_DOWNLOAD \"Enable support for HTTP(S) downloads\" OFF \"WITH_DOWNLOADER\" OFF)\noption(WITH_LWM2M11 \"Enable support for LwM2M 1.1\" ON)\ncmake_dependent_option(WITH_LWM2M12 \"Enable support for LwM2M 1.2 features\" ON \"WITH_LWM2M11\" OFF)\n# NOTE: WITH_EST is moved below due to dependencies\n\nset(THREAD_SAFETY_DEFAULT OFF)\nif(WIN32 OR UNIX)\n set(THREAD_SAFETY_DEFAULT ON)\nendif()\n\noption(WITH_THREAD_SAFETY \"Enable guarding of all accesses to anjay_t with a mutex\" \"${THREAD_SAFETY_DEFAULT}\")\n\n################# LIBRARIES ####################################################\n\n# avs_commons required components.\nset(AVS_COMMONS_COMPONENTS algorithm crypto list buffer net sched stream stream_net url utils compat_threading)\nif(WITH_HTTP_DOWNLOAD)\n list(APPEND AVS_COMMONS_COMPONENTS http)\nendif()\nif(WITH_AVS_PERSISTENCE)\n list(APPEND AVS_COMMONS_COMPONENTS persistence)\nendif()\nif(WITH_MODULE_sim_bootstrap)\n list(APPEND AVS_COMMONS_COMPONENTS stream_md5)\nendif()\nif(NOT DEFINED WITH_AVS_RBTREE OR WITH_AVS_RBTREE)\n set(WITH_AVS_RBTREE ON CACHE INTERNAL \"\")\nendif()\n\nset(AVS_COMMONS_LIBRARIES)\nforeach(_component ${AVS_COMMONS_COMPONENTS})\n string(TOUPPER ${_component} _component_uppercase)\n\n # Enable compilation of each component.\n set(WITH_AVS_${_component_uppercase} ON CACHE INTERNAL \"\")\n\n # And mark it as a weak dependency.\n list(APPEND AVS_COMMONS_LIBRARIES avs_${_component})\nendforeach()\n\noption(WITH_LOCAL_AVS_COMMONS \"Use locally installed avs_commons libraries\" OFF)\n\nif(WITH_LOCAL_AVS_COMMONS)\n # WITH_TEST is also defined in Commons\n # it defaults to ON there, but if we have external avs_commons, let's better not depend on avs_unit by default\n cmake_dependent_option(WITH_TEST \"Enable Anjay tests\" OFF WITH_AVS_UNIT OFF)\n if(WITH_TEST)\n set(AVS_COMMONS_COMPONENTS ${AVS_COMMONS_COMPONENTS} unit)\n\n find_program(VALGRIND_EXECUTABLE valgrind)\n cmake_dependent_option(WITH_VALGRIND \"Enable usage of valgrind during unit tests\" OFF \"VALGRIND_EXECUTABLE\" OFF)\n endif()\n find_package(avs_commons COMPONENTS ${AVS_COMMONS_COMPONENTS} REQUIRED)\n\n function(read_avs_commons_compile_time_option OPTION_NAME)\n file(WRITE ${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/CMakeTmp/avs_commons_check.c\n \"#include \\nint main() {\\n#ifndef ${OPTION_NAME}\\nint error[-1];\\n#endif\\nreturn 0; }\\n\")\n get_target_property(INCLUDE_DIRS avs_utils INTERFACE_INCLUDE_DIRECTORIES)\n try_compile(OPTION_VALUE\n ${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/CMakeTmp\n ${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/CMakeTmp/avs_commons_check.c\n CMAKE_FLAGS \"-DINCLUDE_DIRECTORIES=${INCLUDE_DIRS}\")\n set(${OPTION_NAME} ${OPTION_VALUE} CACHE INTERNAL \"\")\n endfunction()\n\n read_avs_commons_compile_time_option(AVS_COMMONS_HAVE_VISIBILITY)\n read_avs_commons_compile_time_option(AVS_COMMONS_STREAM_WITH_FILE)\n set(WITH_AVS_STREAM_FILE \"${AVS_COMMONS_STREAM_WITH_FILE}\")\n read_avs_commons_compile_time_option(AVS_COMMONS_SCHED_THREAD_SAFE)\n set(WITH_SCHEDULER_THREAD_SAFE \"${AVS_COMMONS_SCHED_THREAD_SAFE}\")\n read_avs_commons_compile_time_option(AVS_COMMONS_NET_WITH_POSIX_AVS_SOCKET)\n set(WITH_POSIX_AVS_SOCKET \"${AVS_COMMONS_NET_WITH_POSIX_AVS_SOCKET}\")\nelse()\n set(_DTLS_BACKENDS \"mbedtls\" \"openssl\" \"tinydtls\" \"custom\")\n set(DTLS_BACKEND \"mbedtls\" CACHE STRING \"DTLS backend to use; possible values: ${_DTLS_BACKENDS}\")\n\n # Reset enabled backends first, to avoid issues with CMakeCache\n set(WITH_CUSTOM_TLS OFF CACHE INTERNAL \"\")\n set(WITH_MBEDTLS OFF CACHE INTERNAL \"\")\n set(WITH_OPENSSL OFF CACHE INTERNAL \"\")\n set(WITH_TINYDTLS OFF CACHE INTERNAL \"\")\n\n string(TOLOWER \"${DTLS_BACKEND}\" _DTLS_BACKEND_LOWERCASE)\n if(_DTLS_BACKEND_LOWERCASE STREQUAL \"mbedtls\")\n set(WITH_MBEDTLS ON CACHE INTERNAL \"\")\n elseif(_DTLS_BACKEND_LOWERCASE STREQUAL \"openssl\")\n set(OPENSSL_CUSTOM_CIPHERS_ENABLED ON CACHE INTERNAL \"\")\n set(WITH_OPENSSL ON CACHE INTERNAL \"\")\n set(WITH_OPENSSL_CUSTOM_CIPHERS \"ECDHE-ECDSA-AES128-CCM8:PSK-AES128-CCM8\" CACHE INTERNAL \"\")\n elseif(_DTLS_BACKEND_LOWERCASE STREQUAL \"tinydtls\")\n set(WITH_TINYDTLS ON CACHE INTERNAL \"\")\n elseif(_DTLS_BACKEND_LOWERCASE STREQUAL \"custom\")\n set(WITH_CUSTOM_TLS ON CACHE INTERNAL \"\")\n elseif(NOT _DTLS_BACKEND_LOWERCASE STREQUAL \"\")\n message(FATAL_ERROR \"Unsupported DTLS backend: ${_DTLS_BACKEND_LOWERCASE}; possible values: ${_DTLS_BACKENDS}\")\n endif()\n\n message(STATUS \"DTLS backend: ${_DTLS_BACKEND_LOWERCASE}\")\n\n if(WITH_MBEDTLS OR WITH_CUSTOM_TLS)\n set(SSL_ERROR_API_DEFAULT ON)\n else()\n set(SSL_ERROR_API_DEFAULT OFF)\n endif()\nendif()\n\noption(WITH_AVS_COAP_TCP \"Enable CoAP over TCP support\" \"${WITH_LWM2M11}\")\noption(WITH_CONN_STATUS_API \"Enable support for the experimental anjay_get_server_connection_status() API and related callback.\" ON)\noption(WITH_SSL_ERROR_API \"Enable support for the experimental server SSL error callback.\" \"${SSL_ERROR_API_DEFAULT}\")\n\n\n\nset(ENABLE_ADVANCED_CRYPTO OFF)\n\noption(WITH_AVS_LOG \"Enable logging support\" ON)\n\nif(NOT WITH_LOCAL_AVS_COMMONS)\n set(WITH_SCHEDULER_THREAD_SAFE \"${WITH_THREAD_SAFETY}\" CACHE INTERNAL \"\")\n set(WITH_AVS_CRYPTO_ADVANCED_FEATURES ${ENABLE_ADVANCED_CRYPTO} CACHE INTERNAL \"\")\n\n add_subdirectory(deps/avs_commons)\nendif()\n\noption(WITH_LOCAL_AVS_COAP \"Use locally installed avs_coap library\" OFF)\nif(WITH_LOCAL_AVS_COAP)\n find_package(avs_coap REQUIRED)\n\n function(read_avs_coap_compile_time_option OPTION_NAME)\n file(WRITE ${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/CMakeTmp/avs_coap_check.c\n \"#include \\nint main() {\\n#ifndef ${OPTION_NAME}\\nint error[-1];\\n#endif\\nreturn 0; }\\n\")\n get_target_property(INCLUDE_DIRS avs_coap INTERFACE_INCLUDE_DIRECTORIES)\n try_compile(OPTION_VALUE\n ${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/CMakeTmp\n ${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/CMakeTmp/avs_coap_check.c\n CMAKE_FLAGS \"-DINCLUDE_DIRECTORIES=${INCLUDE_DIRS}\")\n set(${OPTION_NAME} ${OPTION_VALUE} CACHE INTERNAL \"\")\n endfunction()\n\n read_avs_coap_compile_time_option(WITH_AVS_COAP_UDP)\n read_avs_coap_compile_time_option(WITH_AVS_COAP_TCP)\n read_avs_coap_compile_time_option(WITH_AVS_COAP_OBSERVE)\n read_avs_coap_compile_time_option(WITH_AVS_COAP_BLOCK)\n read_avs_coap_compile_time_option(WITH_AVS_COAP_STREAMING_API)\nelse()\n add_subdirectory(deps/avs_coap)\nendif()\n\nif(NOT WITH_AVS_COAP_STREAMING_API)\n message(FATAL_ERROR \"avs_coap streaming API is required, but disabled\")\nendif()\n\nif(WITH_AVS_LOG)\n list(APPEND AVS_COMMONS_LIBRARIES avs_log)\nendif()\n\n################# FEATURES #####################################################\n\noption(WITH_ACCESS_CONTROL \"Enable core support for Access Control mechanism\" ON)\noption(WITH_DISCOVER \"Enable support for LwM2M Discover operation\" ON)\ncmake_dependent_option(WITH_OBSERVE \"Enable support for Information Reporting interface (Observe)\" ON \"WITH_AVS_COAP_OBSERVE\" OFF)\ncmake_dependent_option(WITH_CON_ATTR \"Enable support for the Confirmable Notification attribute\" \"${WITH_LWM2M12}\" WITH_OBSERVE OFF)\noption(WITH_LEGACY_CONTENT_FORMAT_SUPPORT\n \"Enable support for pre-LwM2M 1.0 CoAP Content-Format values (1541-1543)\" OFF)\noption(WITH_LWM2M_JSON \"Enable support for LwM2M 1.0 JSON (output only)\" ON)\noption(WITHOUT_PLAINTEXT \"Disable support for Plain Text content format\" OFF)\noption(WITHOUT_DEREGISTER \"Disable use of the Deregister message\" OFF)\noption(WITHOUT_IP_STICKINESS \"Disable support for IP stickiness\" OFF)\noption(WITHOUT_COMPOSITE_OPERATIONS \"Disable composite operations\" OFF)\ncmake_dependent_option(WITH_SENML_JSON \"Enable support for SenML JSON content format\" ON WITH_LWM2M11 OFF)\ncmake_dependent_option(WITH_CBOR \"Enable support for CBOR and SenML CBOR content formats\" ON WITH_LWM2M11 OFF)\ncmake_dependent_option(WITH_LWM2M_GATEWAY \"Enable support /25 LwM2M Gateway Object\" OFF \"WITH_LWM2M11;NOT WITH_CORE_PERSISTENCE\" OFF)\ncmake_dependent_option(WITH_BOOTSTRAP_PACK \"Enable LwM2M Bootstrap-Pack support\" ON \"WITH_LWM2M12;WITH_BOOTSTRAP;WITH_CBOR OR WITH_SENML_JSON\" OFF)\ncmake_dependent_option(WITH_SEND \"Enable support for LwM2M 1.1 Send operation\" ON \"WITH_CBOR OR WITH_SENML_JSON\" OFF)\ncmake_dependent_option(WITH_OBSERVATION_ATTRIBUTES \"Enable support for Observation Attributes\" ON \"WITH_OBSERVE;WITH_LWM2M12\" OFF)\noption(WITHOUT_QUEUE_MODE_AUTOCLOSE \"Disable automatic closing of server connection sockets after MAX_TRANSMIT_WAIT of inactivity\" OFF)\n\ncmake_dependent_option(WITH_OBSERVATION_STATUS \"Enable support for anjay_resource_observation_status() API\" ON \"WITH_OBSERVE\" OFF)\ncmake_dependent_option(WITH_COAP_DOWNLOAD \"Enable support for CoAP(S) downloads\" ON WITH_DOWNLOADER OFF)\n\ncmake_dependent_option(WITH_ANJAY_LOGS \"Enable logging support\" ON WITH_AVS_LOG OFF)\ncmake_dependent_option(WITH_ANJAY_TRACE_LOGS \"Enable logging support\" ON \"WITH_ANJAY_LOGS;NOT EXTERNAL_LOG_LEVELS_HEADER\" OFF)\n\ncmake_dependent_option(AVS_LOG_WITH_TRACE \"Enable TRACE level logging\" OFF WITH_AVS_LOG OFF)\ncmake_dependent_option(WITH_INTERNAL_LOGS \"Enable logging from inside AVSystem Commons libraries\" ON WITH_AVS_LOG OFF)\ncmake_dependent_option(WITH_INTERNAL_TRACE \"Enable TRACE-level logs inside AVSystem Commons libraries\" ON AVS_LOG_WITH_TRACE OFF)\n\noption(WITH_NET_STATS \"Enable measuring amount of LwM2M traffic\" ON)\n\noption(WITH_COMMUNICATION_TIMESTAMP_API \"Enable communication timestamps\" ON)\n\noption(WITH_EVENT_LOOP \"Enable default implementation of the event loop\" \"${WITH_POSIX_AVS_SOCKET}\")\n\nif(DEFINED WITH_MODULE_attr_storage)\n message(FATAL_ERROR \"WITH_MODULE_attr_storage has been removed since Anjay 3.0. Please use WITH_ATTR_STORAGE instead.\")\nendif()\n\ncmake_dependent_option(WITH_ATTR_STORAGE \"Enable automatic attribute storage\" ON WITH_AVS_PERSISTENCE OFF)\n\noption(WITH_SECURITY_STRUCTURED \"Enable support for avs_crypto types in the data model\" ON)\n\n# ANJAY_MUTEX_LOCK() variant based on nested functions\nfile(WRITE \"${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/CMakeTmp/nested_funcs.c\"\n \"int main() { int nested(void) { return 0; } return nested(); }\")\ntry_compile(HAVE_NESTED_FUNCTIONS\n \"${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/CMakeTmp\"\n \"${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/CMakeTmp/nested_funcs.c\")\n\nset(WITH_NESTED_FUNCTION_MUTEX_LOCKS_DEFAULT OFF)\nif(WITH_EXTRA_WARNINGS AND NOT CMAKE_BUILD_TYPE MATCHES \"Rel\")\n set(WITH_NESTED_FUNCTION_MUTEX_LOCKS_DEFAULT ON)\nendif()\n\ncmake_dependent_option(WITH_NESTED_FUNCTION_MUTEX_LOCKS\n \"Enable mutex locking variant based on nested functions (provides more compiler warnings)\"\n \"${WITH_NESTED_FUNCTION_MUTEX_LOCKS_DEFAULT}\" \"WITH_THREAD_SAFETY;HAVE_NESTED_FUNCTIONS;AVS_COMMONS_HAVE_PRAGMA_DIAGNOSTIC\" OFF)\n\n# This option is not exposed in anjay_config.h,\n# as it is basically useless outside of development of the Anjay library itself\nif(WITH_NESTED_FUNCTION_MUTEX_LOCKS)\n add_definitions(-DANJAY_WITH_NESTED_FUNCTION_MUTEX_LOCKS)\nendif()\n\n################# MODULES ######################################################\n\n\ncmake_dependent_option(WITH_MODULE_access_control \"Access control object implementation module\" ON WITH_ACCESS_CONTROL OFF)\noption(WITH_MODULE_ipso_objects \"Generic implementation of certain kinds of IPSO objects\" ON)\noption(WITH_MODULE_ipso_objects_v2 \"Experimental generic implementation of certain kinds of IPSO objects\" ON)\noption(WITH_MODULE_security \"Security object module\" ON)\noption(WITH_MODULE_server \"Server object module\" ON)\noption(WITH_MODULE_fw_update \"Firmware Update object module\" ON)\ncmake_dependent_option(WITHOUT_MODULE_fw_update_PUSH_MODE\n \"Disable support for PUSH mode Firmware Update\"\n OFF \"WITH_MODULE_fw_update;WITH_DOWNLOADER\" OFF)\ncmake_dependent_option(WITH_MODULE_fw_update_v11_resources\n \"Enable support for optional resources in Firmware Update object that were added in LwM2M 1.1\"\n OFF \"WITH_LWM2M11\" OFF)\ncmake_dependent_option(WITH_MODULE_factory_provisioning \"Factory provisioning module\" ON \"WITH_BOOTSTRAP;WITH_CBOR\" OFF)\noption(WITH_MODULE_advanced_fw_update \"Advanced Firmware Update object module\" OFF)\noption(WITH_MODULE_sw_mgmt \"Software Management object module\" OFF)\n\n################# CODE #########################################################\n\nadd_library(anjay\n include_public/anjay/access_control.h\n include_public/anjay/advanced_fw_update.h\n include_public/anjay/anjay.h\n include_public/anjay/attr_storage.h\n include_public/anjay/core.h\n include_public/anjay/dm.h\n include_public/anjay/download.h\n include_public/anjay/factory_provisioning.h\n include_public/anjay/fw_update.h\n include_public/anjay/io.h\n include_public/anjay/ipso_objects.h\n include_public/anjay/ipso_objects_v2.h\n include_public/anjay/lwm2m_gateway.h\n include_public/anjay/lwm2m_send.h\n include_public/anjay/security.h\n include_public/anjay/server.h\n include_public/anjay/stats.h\n include_public/anjay/sw_mgmt.h\n src/anjay_config_log.h\n src/anjay_init.h\n src/anjay_modules/anjay_access_utils.h\n src/anjay_modules/anjay_bootstrap.h\n src/anjay_modules/anjay_dm_utils.h\n src/anjay_modules/anjay_io_utils.h\n src/anjay_modules/anjay_notify.h\n src/anjay_modules/anjay_raw_buffer.h\n src/anjay_modules/anjay_sched.h\n src/anjay_modules/anjay_servers.h\n src/anjay_modules/anjay_time_defs.h\n src/anjay_modules/anjay_utils_core.h\n src/anjay_modules/dm/anjay_execute.h\n src/anjay_modules/dm/anjay_modules.h\n src/core/anjay_access_utils.c\n src/core/anjay_access_utils_private.h\n src/core/anjay_bootstrap_core.c\n src/core/anjay_bootstrap_core.h\n src/core/anjay_core.c\n src/core/anjay_core.h\n src/core/anjay_dm_core.c\n src/core/anjay_dm_core.h\n src/core/anjay_downloader.h\n src/core/anjay_event_loop.c\n src/core/anjay_io_core.c\n src/core/anjay_io_core.h\n src/core/anjay_io_utils.c\n src/core/anjay_lwm2m_send.c\n src/core/anjay_lwm2m_send.h\n src/core/anjay_notify.c\n src/core/anjay_raw_buffer.c\n src/core/anjay_servers_inactive.h\n src/core/anjay_servers_private.h\n src/core/anjay_servers_reload.h\n src/core/anjay_servers_utils.c\n src/core/anjay_servers_utils.h\n src/core/anjay_stats.c\n src/core/anjay_stats.h\n src/core/anjay_utils_core.c\n src/core/anjay_utils_private.h\n src/core/attr_storage/anjay_attr_storage.h\n src/core/attr_storage/anjay_attr_storage_persistence.c\n src/core/attr_storage/anjay_attr_storage_private.h\n src/core/attr_storage/anjay_attr_storage.c\n src/core/coap/anjay_content_format.h\n src/core/coap/anjay_msg_details.h\n src/core/dm/anjay_discover.c\n src/core/dm/anjay_discover.h\n src/core/dm/anjay_dm_attributes.c\n src/core/dm/anjay_dm_attributes.h\n src/core/dm/anjay_dm_create.c\n src/core/dm/anjay_dm_create.h\n src/core/dm/anjay_dm_execute.c\n src/core/dm/anjay_dm_execute.h\n src/core/dm/anjay_dm_handlers.c\n src/core/dm/anjay_dm_read.c\n src/core/dm/anjay_dm_read.h\n src/core/dm/anjay_dm_write_attrs.c\n src/core/dm/anjay_dm_write_attrs.h\n src/core/dm/anjay_dm_write.c\n src/core/dm/anjay_dm_write.h\n src/core/dm/anjay_modules.c\n src/core/dm/anjay_query.c\n src/core/dm/anjay_query.h\n src/core/downloader/anjay_coap.c\n src/core/downloader/anjay_downloader.c\n src/core/downloader/anjay_http.c\n src/core/downloader/anjay_private.h\n src/core/io/anjay_base64_out.c\n src/core/io/anjay_base64_out.h\n src/core/io/anjay_batch_builder.c\n src/core/io/anjay_batch_builder.h\n src/core/io/anjay_cbor_in.c\n src/core/io/anjay_cbor_out.c\n src/core/io/anjay_common.c\n src/core/io/anjay_common.h\n src/core/io/anjay_corelnk.c\n src/core/io/anjay_corelnk.h\n src/core/io/anjay_dynamic.c\n src/core/io/anjay_input_buf.c\n src/core/io/anjay_json_encoder.c\n src/core/io/anjay_json_like_decoder.c\n src/core/io/anjay_json_like_decoder.h\n src/core/io/anjay_json_like_decoder_vtable.h\n src/core/io/anjay_lwm2m_cbor_in.c\n src/core/io/anjay_lwm2m_cbor_out.c\n src/core/io/anjay_opaque.c\n src/core/io/anjay_output_buf.c\n src/core/io/anjay_senml_in.c\n src/core/io/anjay_senml_like_encoder.c\n src/core/io/anjay_senml_like_encoder.h\n src/core/io/anjay_senml_like_encoder_vtable.h\n src/core/io/anjay_senml_like_out.c\n src/core/io/anjay_text.c\n src/core/io/anjay_tlv.h\n src/core/io/anjay_tlv_in.c\n src/core/io/anjay_tlv_out.c\n src/core/io/anjay_vtable.h\n src/core/io/cbor/anjay_cbor_encoder_ll.c\n src/core/io/cbor/anjay_cbor_encoder_ll.h\n src/core/io/cbor/anjay_cbor_types.h\n src/core/io/cbor/anjay_json_like_cbor_decoder.c\n src/core/io/cbor/anjay_json_like_cbor_decoder.h\n src/core/io/cbor/anjay_senml_cbor_encoder.c\n src/core/io/json/anjay_json_decoder.c\n src/core/io/json/anjay_json_decoder.h\n src/core/observe/anjay_observe_core.c\n src/core/observe/anjay_observe_core.h\n src/core/observe/anjay_observe_internal.h\n src/core/observe/anjay_observe_planning.c\n src/core/servers/anjay_activate.c\n src/core/servers/anjay_activate.h\n src/core/servers/anjay_connection_ip.c\n src/core/servers/anjay_connections.c\n src/core/servers/anjay_connections.h\n src/core/servers/anjay_connections_internal.h\n src/core/servers/anjay_register.c\n src/core/servers/anjay_register.h\n src/core/servers/anjay_reload.c\n src/core/servers/anjay_security_generic.c\n src/core/servers/anjay_security.h\n src/core/servers/anjay_server_connections.c\n src/core/servers/anjay_server_connections.h\n src/core/servers/anjay_servers_internal.c\n src/core/servers/anjay_servers_internal.h\n src/modules/access_control/anjay_access_control_handlers.c\n src/modules/access_control/anjay_access_control_persistence.c\n src/modules/access_control/anjay_mod_access_control.c\n src/modules/access_control/anjay_mod_access_control.h\n src/modules/advanced_fw_update/anjay_advanced_fw_update.c\n src/modules/factory_provisioning/anjay_provisioning.c\n src/modules/fw_update/anjay_fw_update.c\n src/modules/ipso/anjay_ipso_3d_sensor.c\n src/modules/ipso/anjay_ipso_basic_sensor.c\n src/modules/ipso/anjay_ipso_button.c\n src/modules/ipso_v2/anjay_ipso_v2_3d_sensor.c\n src/modules/ipso_v2/anjay_ipso_v2_basic_sensor.c\n src/modules/lwm2m_gateway/anjay_lwm2m_gateway.c\n src/modules/security/anjay_mod_security.c\n src/modules/security/anjay_mod_security.h\n src/modules/security/anjay_security_persistence.c\n src/modules/security/anjay_security_transaction.c\n src/modules/security/anjay_security_transaction.h\n src/modules/security/anjay_security_utils.c\n src/modules/security/anjay_security_utils.h\n src/modules/server/anjay_mod_server.c\n src/modules/server/anjay_mod_server.h\n src/modules/server/anjay_server_persistence.c\n src/modules/server/anjay_server_transaction.c\n src/modules/server/anjay_server_transaction.h\n src/modules/server/anjay_server_utils.c\n src/modules/server/anjay_server_utils.h\n src/modules/sw_mgmt/anjay_sw_mgmt.c\n )\n\ntarget_include_directories(anjay PUBLIC\n $\n $\n $)\ntarget_include_directories(anjay PRIVATE\n $)\ntarget_link_libraries(anjay PUBLIC avs_coap ${AVS_COMMONS_LIBRARIES})\nset_property(TARGET anjay APPEND PROPERTY COMPILE_DEFINITIONS \"ANJAY_VERSION=\\\"${ANJAY_VERSION}\\\"\")\n\n################# LINK #########################################################\n\nset(ANJAY_WITH_ACCESS_CONTROL \"${WITH_ACCESS_CONTROL}\")\nset(ANJAY_WITH_ATTR_STORAGE \"${WITH_ATTR_STORAGE}\")\nset(ANJAY_WITH_BOOTSTRAP \"${WITH_BOOTSTRAP}\")\nset(ANJAY_WITH_BOOTSTRAP_PACK \"${WITH_BOOTSTRAP_PACK}\")\nset(ANJAY_WITH_COAP_DOWNLOAD \"${WITH_COAP_DOWNLOAD}\")\nset(ANJAY_WITH_CON_ATTR \"${WITH_CON_ATTR}\")\nset(ANJAY_WITH_DISCOVER \"${WITH_DISCOVER}\")\nset(ANJAY_WITH_DOWNLOADER \"${WITH_DOWNLOADER}\")\nset(ANJAY_WITH_HTTP_DOWNLOAD \"${WITH_HTTP_DOWNLOAD}\")\nset(ANJAY_WITH_LEGACY_CONTENT_FORMAT_SUPPORT \"${WITH_LEGACY_CONTENT_FORMAT_SUPPORT}\")\nset(ANJAY_WITH_LOGS \"${WITH_ANJAY_LOGS}\")\nset(ANJAY_WITH_LWM2M_JSON \"${WITH_LWM2M_JSON}\")\nset(ANJAY_WITHOUT_TLV \"${WITHOUT_TLV}\")\nset(ANJAY_WITHOUT_PLAINTEXT \"${WITHOUT_PLAINTEXT}\")\nset(ANJAY_WITHOUT_DEREGISTER \"${WITHOUT_DEREGISTER}\")\nset(ANJAY_WITHOUT_IP_STICKINESS \"${WITHOUT_IP_STICKINESS}\")\nset(ANJAY_WITHOUT_COMPOSITE_OPERATIONS \"${WITHOUT_COMPOSITE_OPERATIONS}\")\nset(ANJAY_WITH_MODULE_ACCESS_CONTROL \"${WITH_MODULE_access_control}\")\nset(ANJAY_WITH_MODULE_IPSO_OBJECTS \"${WITH_MODULE_ipso_objects}\")\nset(ANJAY_WITH_MODULE_IPSO_OBJECTS_V2 \"${WITH_MODULE_ipso_objects_v2}\")\nset(ANJAY_WITH_MODULE_FW_UPDATE \"${WITH_MODULE_fw_update}\")\nset(ANJAY_WITH_MODULE_FW_UPDATE_V11_RESOURCES \"${WITH_MODULE_fw_update_v11_resources}\")\nset(ANJAY_WITH_MODULE_ADVANCED_FW_UPDATE \"${WITH_MODULE_advanced_fw_update}\")\nset(ANJAY_WITHOUT_MODULE_FW_UPDATE_PUSH_MODE \"${WITHOUT_MODULE_fw_update_PUSH_MODE}\")\nset(ANJAY_WITH_MODULE_SECURITY \"${WITH_MODULE_security}\")\nset(ANJAY_WITH_MODULE_SERVER \"${WITH_MODULE_server}\")\nset(ANJAY_WITH_MODULE_SW_MGMT \"${WITH_MODULE_sw_mgmt}\")\nset(ANJAY_WITH_NET_STATS \"${WITH_NET_STATS}\")\nset(ANJAY_WITH_COMMUNICATION_TIMESTAMP_API \"${WITH_COMMUNICATION_TIMESTAMP_API}\")\nset(ANJAY_WITH_EVENT_LOOP \"${WITH_EVENT_LOOP}\")\nset(ANJAY_WITH_OBSERVATION_STATUS \"${WITH_OBSERVATION_STATUS}\")\nset(ANJAY_WITH_OBSERVE \"${WITH_OBSERVE}\")\nset(ANJAY_WITH_THREAD_SAFETY \"${WITH_THREAD_SAFETY}\")\nset(ANJAY_WITH_TRACE_LOGS \"${WITH_ANJAY_TRACE_LOGS}\")\nset(ANJAY_WITH_MODULE_FACTORY_PROVISIONING \"${WITH_MODULE_factory_provisioning}\")\n\nset(ANJAY_WITH_CBOR \"${WITH_CBOR}\")\nset(ANJAY_WITH_LWM2M11 \"${WITH_LWM2M11}\")\nset(ANJAY_WITH_LWM2M12 \"${WITH_LWM2M12}\")\nset(ANJAY_WITH_OBSERVATION_ATTRIBUTES \"${WITH_OBSERVATION_ATTRIBUTES}\")\nset(ANJAY_WITH_SECURITY_STRUCTURED \"${WITH_SECURITY_STRUCTURED}\")\nset(ANJAY_WITH_SEND \"${WITH_SEND}\")\nset(ANJAY_WITH_SENML_JSON \"${WITH_SENML_JSON}\")\nset(ANJAY_WITHOUT_QUEUE_MODE_AUTOCLOSE \"${WITHOUT_QUEUE_MODE_AUTOCLOSE}\")\nset(ANJAY_WITH_CONN_STATUS_API \"${WITH_CONN_STATUS_API}\")\nset(ANJAY_WITH_SSL_ERROR_API \"${WITH_SSL_ERROR_API}\")\nset(ANJAY_WITH_LWM2M_GATEWAY \"${WITH_LWM2M_GATEWAY}\")\n\nconfigure_file(include_public/anjay/anjay_config.h.in\n include_public/anjay/anjay_config.h)\n\nif(BUILD_SHARED_LIBS)\n set_target_properties(anjay PROPERTIES\n VERSION ${ANJAY_BINARY_VERSION})\n if(AVS_COMMONS_HAVE_VISIBILITY)\n get_property(LINK_FLAGS TARGET anjay PROPERTY LINK_FLAGS)\n set_property(TARGET anjay PROPERTY LINK_FLAGS \"${LINK_FLAGS} -Wl,--exclude-libs,ALL\")\n endif()\n if(APPLE)\n get_property(LINK_FLAGS TARGET anjay PROPERTY LINK_FLAGS)\n set_property(TARGET anjay PROPERTY LINK_FLAGS \"${LINK_FLAGS} -Wl,-undefined,dynamic_lookup\")\n endif()\nendif()\n\n################# DEMO #########################################################\n\nset(DEMO_DEPENDENCIES\n WITH_AVS_LOG\n WITH_EVENT_LOOP\n # WITH_SCHEDULER_THREAD_SAFE\n WITH_MODULE_security\n WITH_MODULE_server)\n\ncmake_dependent_option(WITH_DEMO \"Compile DEMO applications\" ON \"${DEMO_DEPENDENCIES}\" OFF)\n\nif(WITH_DEMO)\n find_program(OPENSSL_EXECUTABLE openssl)\n if(OPENSSL_EXECUTABLE)\n if(NOT EXISTS \"${ANJAY_BUILD_OUTPUT_DIR}/certs/client.crt.der\")\n execute_process(COMMAND\n env bash\n \"${CMAKE_CURRENT_SOURCE_DIR}/tools/generate-certs.sh\"\n \"${ANJAY_BUILD_OUTPUT_DIR}/certs\"\n RESULT_VARIABLE RES)\n if(NOT ${RES} EQUAL 0)\n message(FATAL_ERROR \"could not generate SSL certificates\")\n endif()\n endif()\n elseif(WITH_AVS_UNIT)\n message(FATAL_ERROR \"OpenSSL command line utility is required for unit tests\")\n endif()\n\n add_subdirectory(demo)\nendif()\n\n################# TEST ########################################################\n\ncmake_dependent_option(WITH_INTEGRATION_TESTS \"Enable integration tests\" OFF \"WITH_TEST;WITH_DEMO\" OFF)\n\nif(WITH_TEST)\n enable_testing()\n\n add_custom_target(check)\n add_custom_target(anjay_unit_check)\n add_dependencies(check anjay_unit_check)\n\n # anjay_test\n add_executable(anjay_test EXCLUDE_FROM_ALL\n $\n tests/core/coap/utils.c\n tests/core/coap/utils.h\n tests/core/bootstrap_mock.h\n tests/core/io/bigdata.h\n tests/core/observe/observe_mock.h\n tests/core/socket_mock.c\n tests/core/socket_mock.h\n tests/utils/dm.c\n tests/utils/dm.h\n tests/utils/mock_clock.c\n tests/utils/mock_clock.h\n tests/utils/mock_dm.c\n tests/utils/mock_dm.h\n tests/utils/utils.h\n tests/utils/coap/socket.h\n tests/utils/coap/socket.c)\n if(WITH_SENML_JSON)\n target_sources(anjay_test PRIVATE tests/core/io/senml_json_encoder.c)\n endif()\n if(WITH_CBOR)\n target_sources(anjay_test PRIVATE tests/core/io/senml_cbor_encoder.c)\n endif()\n if(WITH_SEND)\n target_sources(anjay_test PRIVATE tests/core/lwm2m_send.c)\n endif()\n if(WITH_MODULE_factory_provisioning)\n target_sources(anjay_test PRIVATE tests/modules/factory_provisioning/provisioning.c)\n endif()\n target_include_directories(anjay_test PRIVATE\n \"${CMAKE_CURRENT_SOURCE_DIR}\"\n $)\n target_link_libraries(anjay_test PRIVATE avs_unit avs_coap_for_tests ${AVS_COMMONS_LIBRARIES})\n\n if(NOT HAVE_DLSYM AND NOT DLSYM_LIBRARY)\n message(FATAL_ERROR \"dlsym() is required for tests, but its definition \"\n \"could not be found; either use -DDLSYM_LIBRARY to select the \"\n \"library or disable tests\")\n elseif(DLSYM_LIBRARY)\n target_link_libraries(anjay_test PRIVATE ${DLSYM_LIBRARY})\n endif()\n set_property(TARGET anjay_test APPEND PROPERTY COMPILE_DEFINITIONS\n ANJAY_TEST\n \"ANJAY_BIN_DIR=\\\"${CMAKE_RUNTIME_OUTPUT_DIRECTORY}\\\"\")\n\n target_compile_options(anjay_test PRIVATE -Wno-overlength-strings -Wno-vla -Wno-c++-compat)\n if(CMAKE_C_COMPILER_ID MATCHES \"GNU\")\n target_compile_options(anjay_test PRIVATE -Wno-jump-misses-init)\n if(CMAKE_C_COMPILER_VERSION VERSION_LESS 4.8)\n target_compile_options(anjay_test PRIVATE -Wno-missing-field-initializers -Wno-uninitialized -Wno-unused-value)\n else()\n # before GCC 4.8 there was no -Wpedantic, only -pedantic; and no way to disable it\n target_compile_options(anjay_test PRIVATE -Wno-pedantic)\n endif()\n endif()\n\n if(WITH_VALGRIND)\n set(VALGRIND ${VALGRIND_EXECUTABLE} --leak-check=full --track-origins=yes -q --error-exitcode=63 --suppressions=${CMAKE_CURRENT_SOURCE_DIR}/valgrind_test.supp)\n endif()\n\n if(VALGRIND)\n set(VALGRIND_LOG ${VALGRIND} --log-file=${ANJAY_BUILD_OUTPUT_DIR}/VALGRIND.anjay_test.log)\n else()\n set(VALGRIND_LOG)\n endif()\n\n add_test(NAME anjay_test\n WORKING_DIRECTORY \"${CMAKE_CURRENT_BINARY_DIR}\"\n COMMAND ${VALGRIND_LOG} $)\n\n add_custom_target(anjay_check COMMAND ${CMAKE_CTEST_COMMAND} -R \"^anjay_test$$\" -V DEPENDS anjay_test)\n add_dependencies(anjay_unit_check anjay_check)\n\n if(TARGET avs_commons_check)\n add_dependencies(check avs_commons_check)\n endif()\n # TODO T2192: rename to avs_coap after migration\n if(TARGET avs_coap_check)\n add_dependencies(check avs_coap_check)\n endif()\n\n # Source validation\n get_target_property(ANJAY_SOURCES anjay SOURCES)\n set(ABSOLUTE_HEADERS)\n foreach(F ${ANJAY_SOURCES})\n add_test(NAME test_anjay_${F}_visibility\n COMMAND deps/avs_commons/test_visibility.py ${F}\n WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR})\n add_test(NAME test_anjay_${F}_headers\n COMMAND deps/avs_commons/test_headers.py ${F} tools/conditional_headers_whitelist.json\n WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR})\n if(F MATCHES [.]h$)\n list(APPEND ABSOLUTE_HEADERS \"${CMAKE_CURRENT_SOURCE_DIR}/${F}\")\n endif()\n endforeach()\n\n add_custom_target(visibility_check COMMAND ${CMAKE_CTEST_COMMAND} -R \"'^test_anjay_.*_visibility$$'\")\n add_dependencies(anjay_unit_check visibility_check)\n\n add_custom_target(headers_check COMMAND ${CMAKE_CTEST_COMMAND} -R \"'^test_anjay_.*_headers$$'\")\n add_dependencies(anjay_unit_check headers_check)\n\n add_test(NAME test_function_duplicates COMMAND ${CMAKE_CURRENT_SOURCE_DIR}/tools/test_duplicates.py ${ABSOLUTE_HEADERS})\n add_test(NAME test_markdown_toc COMMAND ${CMAKE_CURRENT_SOURCE_DIR}/tools/markdown-toc.py --check \"${CMAKE_CURRENT_SOURCE_DIR}/README.md\")\n add_test(NAME test_config_log COMMAND ${CMAKE_CURRENT_SOURCE_DIR}/tools/anjay_config_log_tool.py validate)\n\n add_custom_target(function_duplicates_check COMMAND ${CMAKE_CTEST_COMMAND} -V -R \"'^test_function_duplicates$$'\")\n\n add_custom_target(toc_check COMMAND ${CMAKE_CTEST_COMMAND} -V -R \"'^test_markdown_toc$$'\")\n\n add_custom_target(config_log_check COMMAND ${CMAKE_CTEST_COMMAND} -V -R \"'^test_config_log$$'\")\n\n add_dependencies(anjay_unit_check\n function_duplicates_check\n toc_check\n config_log_check)\n\n\n # Symbol validation\n add_custom_target(symbols_check COMMAND ${CMAKE_CTEST_COMMAND} -R \"'^test_.*_symbols$$'\" --output-on-failure)\n\n if(BUILD_SHARED_LIBS)\n add_test(NAME test_so_symbols COMMAND ${CMAKE_CURRENT_SOURCE_DIR}/deps/avs_commons/test_symbols.sh $ anjay_ ANJAY_ \"__odr_asan[.]\")\n else()\n add_test(NAME test_a_symbols COMMAND ${CMAKE_CURRENT_SOURCE_DIR}/deps/avs_commons/test_symbols.sh $ anjay_ ANJAY_ _anjay_ _ANJAY_ \"__odr_asan[.]\")\n endif()\n add_dependencies(symbols_check anjay)\n add_dependencies(anjay_unit_check symbols_check)\n\n add_custom_target(anjay_extern_c_check COMMAND\n \"${CMAKE_CURRENT_SOURCE_DIR}/deps/avs_commons/tools/check_extern_c.py\" --path \"${CMAKE_CURRENT_SOURCE_DIR}\")\n add_dependencies(anjay_unit_check anjay_extern_c_check)\n\n add_custom_target(anjay_filename_check\n COMMAND ! find src -name \"'*.[ch]'\" | sed -e \"'s|^.*/||'\" | grep -v \"'^anjay_'\"\n COMMAND ! find src -name \"'*.[ch]'\" | sed -e \"'s|^.*/||'\" | sort | uniq -c | grep -v \"'^ *1 '\"\n WORKING_DIRECTORY \"${CMAKE_CURRENT_SOURCE_DIR}\")\n add_dependencies(anjay_check anjay_filename_check)\n\n add_custom_target(symlink_check COMMAND\n \"${CMAKE_CURRENT_SOURCE_DIR}/tools/symlink-check.sh\")\n add_dependencies(anjay_check symlink_check)\n\n # Unit tests\n include(ProcessorCount)\n ProcessorCount(ANJAY_DEFAULT_NPROC)\n\n set(NPROC \"${ANJAY_DEFAULT_NPROC}\" CACHE STRING \"Number of threads for multi-threaded build/test operations\")\n\n add_subdirectory(tests/codegen)\n\n if(WITH_INTEGRATION_TESTS)\n set(TEST_RERUNS 3 CACHE STRING \"Maximal number of times we try to rerun each testsuite\")\n option(TEST_KEEP_SUCCESS_LOGS \"Store all logs from test cases, even if no error happened\" ON)\n add_subdirectory(tests/integration)\n endif()\nelse(WITH_TEST)\n macro(add_anjay_test NAME)\n endmacro()\nendif(WITH_TEST)\n\n################# FUZZ TESTING #################################################\n\nadd_subdirectory(tests/fuzz)\n\nif(WITH_DOCS)\n add_subdirectory(doc)\nendif()\n\n################# STATIC ANALYSIS ##############################################\n\ncmake_dependent_option(WITH_STATIC_ANALYSIS \"Perform static analysis of the codebase on `make check`\" OFF WITH_TEST OFF)\nif(WITH_STATIC_ANALYSIS)\n find_program(SCAN_BUILD_BINARY scan-build)\n if(NOT SCAN_BUILD_BINARY)\n # some systems only have scan-build-x.y, where x.y is the version of LLVM\n # let's try that\n find_program(CLANG_BINARY clang)\n if(CLANG_BINARY)\n avs_temp_name(_fname)\n file(WRITE ${_fname} \"__clang_major__ __clang_minor__\")\n execute_process(COMMAND \"${CLANG_BINARY}\" -E -P -x c ${_fname}\n OUTPUT_VARIABLE CLANG_VERSION_OUTPUT\n OUTPUT_STRIP_TRAILING_WHITESPACE)\n file(REMOVE ${_fname})\n string(REPLACE \" \" \".\" CLANG_VERSION_OUTPUT \"${CLANG_VERSION_OUTPUT}\")\n find_program(SCAN_BUILD_BINARY \"scan-build-${CLANG_VERSION_OUTPUT}\")\n endif()\n endif()\n if(NOT SCAN_BUILD_BINARY)\n message(FATAL_ERROR \"scan-build not found; specify path with -DSCAN_BUILD_BINARY or disable static analysis with -DWITH_STATIC_ANALYSIS=OFF\")\n else()\n add_custom_target(analyze\n COMMAND \"${CMAKE_CURRENT_SOURCE_DIR}/tools/analyze\"\n --output-dir \"${CMAKE_CURRENT_BINARY_DIR}/static-analysis\"\n --scan-build \"${SCAN_BUILD_BINARY}\")\n add_dependencies(check analyze)\n endif()\nendif()\n\ncmake_dependent_option(WITH_FIND_UNUSED_CODE \"Check for unused symbols on `make check`\" ON \"WITH_TEST;UNIX;NOT APPLE\" OFF)\nif(WITH_FIND_UNUSED_CODE)\n add_custom_target(find_unused_code\n COMMAND \"${CMAKE_CURRENT_SOURCE_DIR}/tools/find_unused_code.py\"\n # avs_commons global cleanup functions\n --ignore-symbol \"^_avs_.*_cleanup_global.*_state$$\"\n # hardware crypto PSK support\n --ignore-symbol \"^_avs_crypto_mbedtls_engine_load_psk_\\\\(identity\\\\|key\\\\)$$\"\n # gcc internals\n --ignore-object \".*/crtbegin.o\"\n # external libraries\n --ignore-file \"^/usr/lib/.*$$\")\n add_dependencies(check find_unused_code)\nendif()\n\noption(WITH_EXAMPLES \"Compile and test examples\" ON)\nif(WITH_EXAMPLES)\n add_subdirectory(examples)\nendif()\n\n################# INSTALL ######################################################\n\n# libraries\ninstall(TARGETS anjay EXPORT anjay-targets DESTINATION lib)\n\ninstall(FILES\n \"${CMAKE_CURRENT_BINARY_DIR}/include_public/anjay/anjay_config.h\"\n \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/anjay.h\"\n \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/core.h\"\n \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/dm.h\"\n \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/download.h\"\n \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/io.h\"\n \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/stats.h\"\n DESTINATION include/anjay)\nif(WITH_ATTR_STORAGE)\n install(FILES \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/attr_storage.h\"\n DESTINATION include/anjay)\nendif()\nif(WITH_SEND)\n install(FILES \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/lwm2m_send.h\"\n DESTINATION include/anjay)\nendif()\nif(WITH_LWM2M_GATEWAY)\n install(FILES \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/lwm2m_gateway.h\"\n DESTINATION include/anjay)\nendif()\nif(WITH_MODULE_access_control)\n install(FILES \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/access_control.h\"\n DESTINATION include/anjay)\nendif()\nif(WITH_MODULE_ipso_objects)\n install(FILES \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/ipso_objects.h\"\n DESTINATION include/anjay)\nendif()\nif(WITH_MODULE_ipso_objects_v2)\n install(FILES \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/ipso_objects_v2.h\"\n DESTINATION include/anjay)\nendif()\nif(WITH_MODULE_fw_update)\n install(FILES \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/fw_update.h\"\n DESTINATION include/anjay)\nendif()\nif(WITH_MODULE_advanced_fw_update)\n install(FILES \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/advanced_fw_update.h\"\n DESTINATION include/anjay)\nendif()\nif(WITH_MODULE_security)\n install(FILES \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/security.h\"\n DESTINATION include/anjay)\nendif()\nif(WITH_MODULE_server)\n install(FILES \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/server.h\"\n DESTINATION include/anjay)\nendif()\nif(WITH_MODULE_factory_provisioning)\n install(FILES \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/factory_provisioning.h\"\n DESTINATION include/anjay)\nendif()\nif(WITH_MODULE_sw_mgmt)\n install(FILES \"${CMAKE_CURRENT_SOURCE_DIR}/include_public/anjay/sw_mgmt.h\"\n DESTINATION include/anjay)\nendif()\n\n# install CMake package\nconfigure_file(${CMAKE_CURRENT_SOURCE_DIR}/cmake/anjay-config.cmake.in\n ${ANJAY_BUILD_OUTPUT_DIR}/cmake/anjay-config.cmake\n @ONLY)\nconfigure_file(${CMAKE_CURRENT_SOURCE_DIR}/cmake/anjay-version.cmake.in\n ${ANJAY_BUILD_OUTPUT_DIR}/cmake/anjay-version.cmake\n @ONLY)\n\ninstall(EXPORT anjay-targets DESTINATION lib/anjay)\ninstall(FILES\n ${ANJAY_BUILD_OUTPUT_DIR}/cmake/anjay-config.cmake\n ${ANJAY_BUILD_OUTPUT_DIR}/cmake/anjay-version.cmake\n DESTINATION lib/anjay)\n" }, { "path": "CONTRIBUTING.rst", "content": "..\n Copyright 2017-2026 AVSystem \n AVSystem Anjay LwM2M SDK\n All rights reserved.\n\n Licensed under AVSystem Anjay LwM2M Client SDK - Non-Commercial License.\n See the attached LICENSE file for details.\n\nContributing to Anjay\n=====================\n\nThank you for considering contributing to Anjay!\n\nPlease take a moment to review this document in order to make the contribution process easy and effective for everyone involved.\n\nFollowing these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.\n\n\nReporting issues\n----------------\n\n**If you find a security vulnerability, do NOT open an issue!** Please email `opensource@avsystem.com `_ instead. We will address the issue as soon as possible and will give you an estimate for when we have a fix and release available for an eventual public disclosure.\n\nUse GitHub issue tracker for reporting other bugs. A great bug report should include:\n\n- Affected library version.\n- Platform information:\n\n - processor architecture,\n - operating system,\n - compiler version.\n- Minimal code example or a list of steps required to reproduce the bug.\n- In case of run-time errors, logs from ``strace``, ``valgrind`` and PCAP network traffic dumps are greatly appreciated.\n\n\nFeature requests\n----------------\n\nIf you think some feature is missing, or that something can be improved, do not hesitate to suggest how we can make it better! When doing that, use GitHub issue tracker to post a description of the feature and some explanation why you need it.\n\n\nCode contributions\n------------------\n\nIf you never submitted a pull request before, take a look at `this fantastic tutorial `_.\n\n#. Fork the project.\n#. Work on your contribution - follow guidelines described below.\n#. Push changes to your fork.\n#. Make sure all ``make check`` tests still pass.\n#. `Create a pull request `_.\n#. Wait for someone from Anjay team to review your contribution and give feedback.\n\n\nCode style\n^^^^^^^^^^\n\nAll code should be fully C99-compliant and compile without warnings under ``gcc`` and ``clang``. Enable extra warnings by using ``cmake -DWITH_EXTRA_WARNINGS=ON`` or ``devconfig`` script. Compiling and testing the code on multiple architectures (e.g. 32/64-bit x86, ARM, MIPS) is not required, but welcome.\n\n\nGeneral guidelines\n``````````````````\n- Do not use GNU extensions.\n- Use ``UPPER_CASE`` for constants and ``snake_case`` in all other cases.\n- Prefer ``static`` functions. Use ``_anjay_`` prefix for private functions shared between translation units and ``anjay_`` prefix for types and public functions.\n- Do not use global variables. Only constants are allowed in global scope.\n- When using bitfields, make sure they are not saved to persistent storage nor sent over the network - their memory layout is implementation-defined, making them non-portable.\n- Avoid recursion - when writing code for an embedded platform, it is important to determine a hard limit on the stack space used by a program.\n- Include license information at the top of each file you add.\n- Use visibility macros defined in ``anjay_init.h`` to prevent internal symbols from being exported when using a GCC-compatible compiler. See `Visibility macros`_ section for examples.\n\n\nVisibility macros\n`````````````````\n- Public header files (``.h`` files inside ``include_public/`` directories): no visibility macros.\n- Private header files (``.h`` files outside ``include_public/`` directories)::\n\n // ... includes\n\n VISIBILITY_PRIVATE_HEADER_BEGIN\n\n // ... code\n\n VISIBILITY_PRIVATE_HEADER_END\n\n\n- Source files (``.c``)::\n\n #include \n\n // ... includes\n\n VISIBILITY_SOURCE_BEGIN\n\n // ... code\n\n\nTests\n^^^^^\n\nMake use of the `coverage script `_ to generate a code coverage report. New code should be covered by tests.\n\nBefore submitting your code, run the whole test suite (``make check``) to ensure that it does not introduce regressions. Use ``valgrind`` and Address Sanitizer to check for memory corruption errors.\n\nRunning tests on Ubuntu 20.04 or later: ::\n\n # Install these for tests:\n sudo apt-get install python3-pip git libmbedtls-dev libssl-dev zlib1g-dev python3 libpython3-dev wget valgrind curl cmake build-essential tshark\n pip3 install -U -r requirements.txt\n # Configure and run check target\n ./devconfig && make check\n\nRunning tests on CentOS 7 or later: ::\n\n # Install these for tests:\n # (IUS is required for Python 3.5)\n sudo yum install -y https://repo.ius.io/ius-release-el7.rpm\n sudo yum install -y valgrind valgrind-devel openssl openssl-devel python35u python35u-devel python35u-pip clang-analyzer\n # Some test scripts expect Python >=3.5 to be available via `python3` command\n # Use update-alternatives to create a /usr/bin/python3 symlink with priority 0\n # (lowest possible)\n sudo update-alternatives --install /usr/bin/python3 python3 /usr/bin/python3.5 0\n sudo python3 -m pip install -r requirements.txt\n\n # Configure and run check target\n # NOTE: clang-3.4 static analyzer (default version for CentOS) gives false\n # positives. --without-analysis flag disables static analysis.\n ./devconfig --without-analysis -DPython_ADDITIONAL_VERSIONS=3.5 && make check\n\nRunning tests on macOS Sierra or later: ::\n\n # Install these for tests:\n brew install python3 openssl llvm\n pip3 install -r requirements.txt\n\n # Configure and run check target:\n # if the scan-build script is located somewhere else, then you need to\n # specify a different SCAN_BUILD_BINARY. Below, we are assumming scan-build\n # comes from an llvm package, installed via homebrew.\n ./devconfig -DSCAN_BUILD_BINARY=/usr/local/Cellar/llvm/*/bin/scan-build && make check\n" }, { "path": "Dockerfile", "content": "# Copyright 2017-2026 AVSystem \n# AVSystem Anjay LwM2M SDK\n# All rights reserved.\n#\n# Licensed under AVSystem Anjay LwM2M Client SDK - Non-Commercial License.\n# See the attached LICENSE file for details.\n\n\nFROM ubuntu:24.04\n\nWORKDIR /Anjay\n\nRUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -yq git build-essential cmake libmbedtls-dev zlib1g-dev\n\nCOPY . .\n\nRUN cmake .\nRUN make -j\n\nENV HOME /Anjay\n\n" }, { "path": "Doxyfile.in", "content": "# Doxyfile 1.9.8\n\n# This file describes the settings to be used by the documentation system\n# doxygen (www.doxygen.org) for a project.\n#\n# All text after a double hash (##) is considered a comment and is placed in\n# front of the TAG it is preceding.\n#\n# All text after a single hash (#) is considered a comment and will be ignored.\n# The format is:\n# TAG = value [value, ...]\n# For lists, items can also be appended using:\n# TAG += value [value, ...]\n# Values that contain spaces should be placed between quotes (\\\" \\\").\n#\n# Note:\n#\n# Use doxygen to compare the used configuration file with the template\n# configuration file:\n# doxygen -x [configFile]\n# Use doxygen to compare the used configuration file with the template\n# configuration file without replacing the environment variables or CMake type\n# replacement variables:\n# doxygen -x_noenv [configFile]\n\n#---------------------------------------------------------------------------\n# Project related configuration options\n#---------------------------------------------------------------------------\n\n# This tag specifies the encoding used for all characters in the configuration\n# file that follow. The default is UTF-8 which is also the encoding used for all\n# text before the first occurrence of this tag. Doxygen uses libiconv (or the\n# iconv built into libc) for the transcoding. See\n# https://www.gnu.org/software/libiconv/ for the list of possible encodings.\n# The default value is: UTF-8.\n\nDOXYFILE_ENCODING = UTF-8\n\n# The PROJECT_NAME tag is a single word (or a sequence of words surrounded by\n# double-quotes, unless you are using Doxywizard) that should identify the\n# project for which the documentation is generated. This name is used in the\n# title of most generated pages and in a few other places.\n# The default value is: My Project.\n\nPROJECT_NAME = anjay\n\n# The PROJECT_NUMBER tag can be used to enter a project or revision number. This\n# could be handy for archiving the generated documentation or if some version\n# control system is used.\n\nPROJECT_NUMBER =\n\n# Using the PROJECT_BRIEF tag one can provide an optional one line description\n# for a project that appears at the top of each page and should give viewer a\n# quick idea about the purpose of the project. Keep the description short.\n\nPROJECT_BRIEF =\n\n# With the PROJECT_LOGO tag one can specify a logo or an icon that is included\n# in the documentation. The maximum height of the logo should not exceed 55\n# pixels and the maximum width should not exceed 200 pixels. Doxygen will copy\n# the logo to the output directory.\n\nPROJECT_LOGO =\n\n# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path\n# into which the generated documentation will be written. If a relative path is\n# entered, it will be relative to the location where doxygen was started. If\n# left blank the current directory will be used.\n\nOUTPUT_DIRECTORY = @DOXYGEN_OUTPUT_DIR@\n\n# If the CREATE_SUBDIRS tag is set to YES then doxygen will create up to 4096\n# sub-directories (in 2 levels) under the output directory of each output format\n# and will distribute the generated files over these directories. Enabling this\n# option can be useful when feeding doxygen a huge amount of source files, where\n# putting all generated files in the same directory would otherwise causes\n# performance problems for the file system. Adapt CREATE_SUBDIRS_LEVEL to\n# control the number of sub-directories.\n# The default value is: NO.\n\nCREATE_SUBDIRS = NO\n\n# Controls the number of sub-directories that will be created when\n# CREATE_SUBDIRS tag is set to YES. Level 0 represents 16 directories, and every\n# level increment doubles the number of directories, resulting in 4096\n# directories at level 8 which is the default and also the maximum value. The\n# sub-directories are organized in 2 levels, the first level always has a fixed\n# number of 16 directories.\n# Minimum value: 0, maximum value: 8, default value: 8.\n# This tag requires that the tag CREATE_SUBDIRS is set to YES.\n\nCREATE_SUBDIRS_LEVEL = 8\n\n# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII\n# characters to appear in the names of generated files. If set to NO, non-ASCII\n# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode\n# U+3044.\n# The default value is: NO.\n\nALLOW_UNICODE_NAMES = NO\n\n# The OUTPUT_LANGUAGE tag is used to specify the language in which all\n# documentation generated by doxygen is written. Doxygen will use this\n# information to generate all constant output in the proper language.\n# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Bulgarian,\n# Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, English\n# (United States), Esperanto, Farsi (Persian), Finnish, French, German, Greek,\n# Hindi, Hungarian, Indonesian, Italian, Japanese, Japanese-en (Japanese with\n# English messages), Korean, Korean-en (Korean with English messages), Latvian,\n# Lithuanian, Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese,\n# Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish,\n# Swedish, Turkish, Ukrainian and Vietnamese.\n# The default value is: English.\n\nOUTPUT_LANGUAGE = English\n\n# If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member\n# descriptions after the members that are listed in the file and class\n# documentation (similar to Javadoc). Set to NO to disable this.\n# The default value is: YES.\n\nBRIEF_MEMBER_DESC = YES\n\n# If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief\n# description of a member or function before the detailed description\n#\n# Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the\n# brief descriptions will be completely suppressed.\n# The default value is: YES.\n\nREPEAT_BRIEF = YES\n\n# This tag implements a quasi-intelligent brief description abbreviator that is\n# used to form the text in various listings. Each string in this list, if found\n# as the leading text of the brief description, will be stripped from the text\n# and the result, after processing the whole list, is used as the annotated\n# text. Otherwise, the brief description is used as-is. If left blank, the\n# following values are used ($name is automatically replaced with the name of\n# the entity):The $name class, The $name widget, The $name file, is, provides,\n# specifies, contains, represents, a, an and the.\n\nABBREVIATE_BRIEF = \"The $name class\" \\\n \"The $name widget\" \\\n \"The $name file\" \\\n is \\\n provides \\\n specifies \\\n contains \\\n represents \\\n a \\\n an \\\n the\n\n# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then\n# doxygen will generate a detailed section even if there is only a brief\n# description.\n# The default value is: NO.\n\nALWAYS_DETAILED_SEC = NO\n\n# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all\n# inherited members of a class in the documentation of that class as if those\n# members were ordinary class members. Constructors, destructors and assignment\n# operators of the base classes will not be shown.\n# The default value is: NO.\n\nINLINE_INHERITED_MEMB = NO\n\n# If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path\n# before files name in the file list and in the header files. If set to NO the\n# shortest path that makes the file name unique will be used\n# The default value is: YES.\n\nFULL_PATH_NAMES = YES\n\n# The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.\n# Stripping is only done if one of the specified strings matches the left-hand\n# part of the path. The tag can be used to show relative paths in the file list.\n# If left blank the directory from which doxygen is run is used as the path to\n# strip.\n#\n# Note that you can specify absolute paths here, but also relative paths, which\n# will be relative from the directory where doxygen is started.\n# This tag requires that the tag FULL_PATH_NAMES is set to YES.\n\nSTRIP_FROM_PATH = @DOXYGEN_INPUT_PATHS@\n\n# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the\n# path mentioned in the documentation of a class, which tells the reader which\n# header file to include in order to use a class. If left blank only the name of\n# the header file containing the class definition is used. Otherwise one should\n# specify the list of include paths that are normally passed to the compiler\n# using the -I flag.\n\nSTRIP_FROM_INC_PATH =\n\n# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but\n# less readable) file names. This can be useful is your file systems doesn't\n# support long names like on DOS, Mac, or CD-ROM.\n# The default value is: NO.\n\nSHORT_NAMES = NO\n\n# If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the\n# first line (until the first dot) of a Javadoc-style comment as the brief\n# description. If set to NO, the Javadoc-style will behave just like regular Qt-\n# style comments (thus requiring an explicit @brief command for a brief\n# description.)\n# The default value is: NO.\n\nJAVADOC_AUTOBRIEF = NO\n\n# If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line\n# such as\n# /***************\n# as being the beginning of a Javadoc-style comment \"banner\". If set to NO, the\n# Javadoc-style will behave just like regular comments and it will not be\n# interpreted by doxygen.\n# The default value is: NO.\n\nJAVADOC_BANNER = NO\n\n# If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first\n# line (until the first dot) of a Qt-style comment as the brief description. If\n# set to NO, the Qt-style will behave just like regular Qt-style comments (thus\n# requiring an explicit \\brief command for a brief description.)\n# The default value is: NO.\n\nQT_AUTOBRIEF = NO\n\n# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a\n# multi-line C++ special comment block (i.e. a block of //! or /// comments) as\n# a brief description. This used to be the default behavior. The new default is\n# to treat a multi-line C++ comment block as a detailed description. Set this\n# tag to YES if you prefer the old behavior instead.\n#\n# Note that setting this tag to YES also means that rational rose comments are\n# not recognized any more.\n# The default value is: NO.\n\nMULTILINE_CPP_IS_BRIEF = NO\n\n# By default Python docstrings are displayed as preformatted text and doxygen's\n# special commands cannot be used. By setting PYTHON_DOCSTRING to NO the\n# doxygen's special commands can be used and the contents of the docstring\n# documentation blocks is shown as doxygen documentation.\n# The default value is: YES.\n\nPYTHON_DOCSTRING = YES\n\n# If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the\n# documentation from any documented member that it re-implements.\n# The default value is: YES.\n\nINHERIT_DOCS = YES\n\n# If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new\n# page for each member. If set to NO, the documentation of a member will be part\n# of the file/class/namespace that contains it.\n# The default value is: NO.\n\nSEPARATE_MEMBER_PAGES = NO\n\n# The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen\n# uses this value to replace tabs by spaces in code fragments.\n# Minimum value: 1, maximum value: 16, default value: 4.\n\nTAB_SIZE = 8\n\n# This tag can be used to specify a number of aliases that act as commands in\n# the documentation. An alias has the form:\n# name=value\n# For example adding\n# \"sideeffect=@par Side Effects:^^\"\n# will allow you to put the command \\sideeffect (or @sideeffect) in the\n# documentation, which will result in a user-defined paragraph with heading\n# \"Side Effects:\". Note that you cannot put \\n's in the value part of an alias\n# to insert newlines (in the resulting output). You can put ^^ in the value part\n# of an alias to insert a newline as if a physical newline was in the original\n# file. When you need a literal { or } or , in the value part of an alias you\n# have to escape them by means of a backslash (\\), this can lead to conflicts\n# with the commands \\{ and \\} for these it is advised to use the version @{ and\n# @} or use a double escape (\\\\{ and \\\\})\n\nALIASES += \"experimental=\\xrefitem experimentals \\\"Experimental\\\" \\\"Experimental List\\\"\" \n\n# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources\n# only. Doxygen will then generate output that is more tailored for C. For\n# instance, some of the names that are used will be different. The list of all\n# members will be omitted, etc.\n# The default value is: NO.\n\nOPTIMIZE_OUTPUT_FOR_C = YES\n\n# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or\n# Python sources only. Doxygen will then generate output that is more tailored\n# for that language. For instance, namespaces will be presented as packages,\n# qualified scopes will look different, etc.\n# The default value is: NO.\n\nOPTIMIZE_OUTPUT_JAVA = NO\n\n# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran\n# sources. Doxygen will then generate output that is tailored for Fortran.\n# The default value is: NO.\n\nOPTIMIZE_FOR_FORTRAN = NO\n\n# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL\n# sources. Doxygen will then generate output that is tailored for VHDL.\n# The default value is: NO.\n\nOPTIMIZE_OUTPUT_VHDL = NO\n\n# Set the OPTIMIZE_OUTPUT_SLICE tag to YES if your project consists of Slice\n# sources only. Doxygen will then generate output that is more tailored for that\n# language. For instance, namespaces will be presented as modules, types will be\n# separated into more groups, etc.\n# The default value is: NO.\n\nOPTIMIZE_OUTPUT_SLICE = NO\n\n# Doxygen selects the parser to use depending on the extension of the files it\n# parses. With this tag you can assign which parser to use for a given\n# extension. Doxygen has a built-in mapping, but you can override or extend it\n# using this tag. The format is ext=language, where ext is a file extension, and\n# language is one of the parsers supported by doxygen: IDL, Java, JavaScript,\n# Csharp (C#), C, C++, Lex, D, PHP, md (Markdown), Objective-C, Python, Slice,\n# VHDL, Fortran (fixed format Fortran: FortranFixed, free formatted Fortran:\n# FortranFree, unknown formatted Fortran: Fortran. In the later case the parser\n# tries to guess whether the code is fixed or free formatted code, this is the\n# default for Fortran type files). For instance to make doxygen treat .inc files\n# as Fortran files (default is PHP), and .f files as C (default is Fortran),\n# use: inc=Fortran f=C.\n#\n# Note: For files without extension you can use no_extension as a placeholder.\n#\n# Note that for custom extensions you also need to set FILE_PATTERNS otherwise\n# the files are not read by doxygen. When specifying no_extension you should add\n# * to the FILE_PATTERNS.\n#\n# Note see also the list of default file extension mappings.\n\nEXTENSION_MAPPING =\n\n# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments\n# according to the Markdown format, which allows for more readable\n# documentation. See https://daringfireball.net/projects/markdown/ for details.\n# The output of markdown processing is further processed by doxygen, so you can\n# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in\n# case of backward compatibilities issues.\n# The default value is: YES.\n\nMARKDOWN_SUPPORT = YES\n\n# When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up\n# to that level are automatically included in the table of contents, even if\n# they do not have an id attribute.\n# Note: This feature currently applies only to Markdown headings.\n# Minimum value: 0, maximum value: 99, default value: 5.\n# This tag requires that the tag MARKDOWN_SUPPORT is set to YES.\n\nTOC_INCLUDE_HEADINGS = 5\n\n# The MARKDOWN_ID_STYLE tag can be used to specify the algorithm used to\n# generate identifiers for the Markdown headings. Note: Every identifier is\n# unique.\n# Possible values are: DOXYGEN use a fixed 'autotoc_md' string followed by a\n# sequence number starting at 0 and GITHUB use the lower case version of title\n# with any whitespace replaced by '-' and punctuation characters removed.\n# The default value is: DOXYGEN.\n# This tag requires that the tag MARKDOWN_SUPPORT is set to YES.\n\nMARKDOWN_ID_STYLE = DOXYGEN\n\n# When enabled doxygen tries to link words that correspond to documented\n# classes, or namespaces to their corresponding documentation. Such a link can\n# be prevented in individual cases by putting a % sign in front of the word or\n# globally by setting AUTOLINK_SUPPORT to NO.\n# The default value is: YES.\n\nAUTOLINK_SUPPORT = YES\n\n# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want\n# to include (a tag file for) the STL sources as input, then you should set this\n# tag to YES in order to let doxygen match functions declarations and\n# definitions whose arguments contain STL classes (e.g. func(std::string);\n# versus func(std::string) {}). This also make the inheritance and collaboration\n# diagrams that involve STL classes more complete and accurate.\n# The default value is: NO.\n\nBUILTIN_STL_SUPPORT = NO\n\n# If you use Microsoft's C++/CLI language, you should set this option to YES to\n# enable parsing support.\n# The default value is: NO.\n\nCPP_CLI_SUPPORT = NO\n\n# Set the SIP_SUPPORT tag to YES if your project consists of sip (see:\n# https://www.riverbankcomputing.com/software/sip/intro) sources only. Doxygen\n# will parse them like normal C++ but will assume all classes use public instead\n# of private inheritance when no explicit protection keyword is present.\n# The default value is: NO.\n\nSIP_SUPPORT = NO\n\n# For Microsoft's IDL there are propget and propput attributes to indicate\n# getter and setter methods for a property. Setting this option to YES will make\n# doxygen to replace the get and set methods by a property in the documentation.\n# This will only work if the methods are indeed getting or setting a simple\n# type. If this is not the case, or you want to show the methods anyway, you\n# should set this option to NO.\n# The default value is: YES.\n\nIDL_PROPERTY_SUPPORT = YES\n\n# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC\n# tag is set to YES then doxygen will reuse the documentation of the first\n# member in the group (if any) for the other members of the group. By default\n# all members of a group must be documented explicitly.\n# The default value is: NO.\n\nDISTRIBUTE_GROUP_DOC = NO\n\n# If one adds a struct or class to a group and this option is enabled, then also\n# any nested class or struct is added to the same group. By default this option\n# is disabled and one has to add nested compounds explicitly via \\ingroup.\n# The default value is: NO.\n\nGROUP_NESTED_COMPOUNDS = NO\n\n# Set the SUBGROUPING tag to YES to allow class member groups of the same type\n# (for instance a group of public functions) to be put as a subgroup of that\n# type (e.g. under the Public Functions section). Set it to NO to prevent\n# subgrouping. Alternatively, this can be done per class using the\n# \\nosubgrouping command.\n# The default value is: YES.\n\nSUBGROUPING = YES\n\n# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions\n# are shown inside the group in which they are included (e.g. using \\ingroup)\n# instead of on a separate page (for HTML and Man pages) or section (for LaTeX\n# and RTF).\n#\n# Note that this feature does not work in combination with\n# SEPARATE_MEMBER_PAGES.\n# The default value is: NO.\n\nINLINE_GROUPED_CLASSES = NO\n\n# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions\n# with only public data fields or simple typedef fields will be shown inline in\n# the documentation of the scope in which they are defined (i.e. file,\n# namespace, or group documentation), provided this scope is documented. If set\n# to NO, structs, classes, and unions are shown on a separate page (for HTML and\n# Man pages) or section (for LaTeX and RTF).\n# The default value is: NO.\n\nINLINE_SIMPLE_STRUCTS = NO\n\n# When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or\n# enum is documented as struct, union, or enum with the name of the typedef. So\n# typedef struct TypeS {} TypeT, will appear in the documentation as a struct\n# with name TypeT. When disabled the typedef will appear as a member of a file,\n# namespace, or class. And the struct will be named TypeS. This can typically be\n# useful for C code in case the coding convention dictates that all compound\n# types are typedef'ed and only the typedef is referenced, never the tag name.\n# The default value is: NO.\n\nTYPEDEF_HIDES_STRUCT = NO\n\n# The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This\n# cache is used to resolve symbols given their name and scope. Since this can be\n# an expensive process and often the same symbol appears multiple times in the\n# code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small\n# doxygen will become slower. If the cache is too large, memory is wasted. The\n# cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range\n# is 0..9, the default is 0, corresponding to a cache size of 2^16=65536\n# symbols. At the end of a run doxygen will report the cache usage and suggest\n# the optimal cache size from a speed point of view.\n# Minimum value: 0, maximum value: 9, default value: 0.\n\nLOOKUP_CACHE_SIZE = 0\n\n# The NUM_PROC_THREADS specifies the number of threads doxygen is allowed to use\n# during processing. When set to 0 doxygen will based this on the number of\n# cores available in the system. You can set it explicitly to a value larger\n# than 0 to get more control over the balance between CPU load and processing\n# speed. At this moment only the input processing can be done using multiple\n# threads. Since this is still an experimental feature the default is set to 1,\n# which effectively disables parallel processing. Please report any issues you\n# encounter. Generating dot graphs in parallel is controlled by the\n# DOT_NUM_THREADS setting.\n# Minimum value: 0, maximum value: 32, default value: 1.\n\nNUM_PROC_THREADS = 1\n\n# If the TIMESTAMP tag is set different from NO then each generated page will\n# contain the date or date and time when the page was generated. Setting this to\n# NO can help when comparing the output of multiple runs.\n# Possible values are: YES, NO, DATETIME and DATE.\n# The default value is: NO.\n\nTIMESTAMP = NO\n\n#---------------------------------------------------------------------------\n# Build related configuration options\n#---------------------------------------------------------------------------\n\n# If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in\n# documentation are documented, even if no documentation was available. Private\n# class members and static file members will be hidden unless the\n# EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.\n# Note: This will also disable the warnings about undocumented members that are\n# normally produced when WARNINGS is set to YES.\n# The default value is: NO.\n\nEXTRACT_ALL = YES\n\n# If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will\n# be included in the documentation.\n# The default value is: NO.\n\nEXTRACT_PRIVATE = NO\n\n# If the EXTRACT_PRIV_VIRTUAL tag is set to YES, documented private virtual\n# methods of a class will be included in the documentation.\n# The default value is: NO.\n\nEXTRACT_PRIV_VIRTUAL = NO\n\n# If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal\n# scope will be included in the documentation.\n# The default value is: NO.\n\nEXTRACT_PACKAGE = NO\n\n# If the EXTRACT_STATIC tag is set to YES, all static members of a file will be\n# included in the documentation.\n# The default value is: NO.\n\nEXTRACT_STATIC = YES\n\n# If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined\n# locally in source files will be included in the documentation. If set to NO,\n# only classes defined in header files are included. Does not have any effect\n# for Java sources.\n# The default value is: YES.\n\nEXTRACT_LOCAL_CLASSES = YES\n\n# This flag is only useful for Objective-C code. If set to YES, local methods,\n# which are defined in the implementation section but not in the interface are\n# included in the documentation. If set to NO, only methods in the interface are\n# included.\n# The default value is: NO.\n\nEXTRACT_LOCAL_METHODS = NO\n\n# If this flag is set to YES, the members of anonymous namespaces will be\n# extracted and appear in the documentation as a namespace called\n# 'anonymous_namespace{file}', where file will be replaced with the base name of\n# the file that contains the anonymous namespace. By default anonymous namespace\n# are hidden.\n# The default value is: NO.\n\nEXTRACT_ANON_NSPACES = NO\n\n# If this flag is set to YES, the name of an unnamed parameter in a declaration\n# will be determined by the corresponding definition. By default unnamed\n# parameters remain unnamed in the output.\n# The default value is: YES.\n\nRESOLVE_UNNAMED_PARAMS = YES\n\n# If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all\n# undocumented members inside documented classes or files. If set to NO these\n# members will be included in the various overviews, but no documentation\n# section is generated. This option has no effect if EXTRACT_ALL is enabled.\n# The default value is: NO.\n\nHIDE_UNDOC_MEMBERS = NO\n\n# If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all\n# undocumented classes that are normally visible in the class hierarchy. If set\n# to NO, these classes will be included in the various overviews. This option\n# will also hide undocumented C++ concepts if enabled. This option has no effect\n# if EXTRACT_ALL is enabled.\n# The default value is: NO.\n\nHIDE_UNDOC_CLASSES = NO\n\n# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend\n# declarations. If set to NO, these declarations will be included in the\n# documentation.\n# The default value is: NO.\n\nHIDE_FRIEND_COMPOUNDS = NO\n\n# If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any\n# documentation blocks found inside the body of a function. If set to NO, these\n# blocks will be appended to the function's detailed documentation block.\n# The default value is: NO.\n\nHIDE_IN_BODY_DOCS = NO\n\n# The INTERNAL_DOCS tag determines if documentation that is typed after a\n# \\internal command is included. If the tag is set to NO then the documentation\n# will be excluded. Set it to YES to include the internal documentation.\n# The default value is: NO.\n\nINTERNAL_DOCS = NO\n\n# With the correct setting of option CASE_SENSE_NAMES doxygen will better be\n# able to match the capabilities of the underlying filesystem. In case the\n# filesystem is case sensitive (i.e. it supports files in the same directory\n# whose names only differ in casing), the option must be set to YES to properly\n# deal with such files in case they appear in the input. For filesystems that\n# are not case sensitive the option should be set to NO to properly deal with\n# output files written for symbols that only differ in casing, such as for two\n# classes, one named CLASS and the other named Class, and to also support\n# references to files without having to specify the exact matching casing. On\n# Windows (including Cygwin) and MacOS, users should typically set this option\n# to NO, whereas on Linux or other Unix flavors it should typically be set to\n# YES.\n# Possible values are: SYSTEM, NO and YES.\n# The default value is: SYSTEM.\n\nCASE_SENSE_NAMES = SYSTEM\n\n# If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with\n# their full class and namespace scopes in the documentation. If set to YES, the\n# scope will be hidden.\n# The default value is: NO.\n\nHIDE_SCOPE_NAMES = YES\n\n# If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will\n# append additional text to a page's title, such as Class Reference. If set to\n# YES the compound reference will be hidden.\n# The default value is: NO.\n\nHIDE_COMPOUND_REFERENCE= NO\n\n# If the SHOW_HEADERFILE tag is set to YES then the documentation for a class\n# will show which file needs to be included to use the class.\n# The default value is: YES.\n\nSHOW_HEADERFILE = YES\n\n# If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of\n# the files that are included by a file in the documentation of that file.\n# The default value is: YES.\n\nSHOW_INCLUDE_FILES = YES\n\n# If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each\n# grouped member an include statement to the documentation, telling the reader\n# which file to include in order to use the member.\n# The default value is: NO.\n\nSHOW_GROUPED_MEMB_INC = NO\n\n# If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include\n# files with double quotes in the documentation rather than with sharp brackets.\n# The default value is: NO.\n\nFORCE_LOCAL_INCLUDES = NO\n\n# If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the\n# documentation for inline members.\n# The default value is: YES.\n\nINLINE_INFO = YES\n\n# If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the\n# (detailed) documentation of file and class members alphabetically by member\n# name. If set to NO, the members will appear in declaration order.\n# The default value is: YES.\n\nSORT_MEMBER_DOCS = YES\n\n# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief\n# descriptions of file, namespace and class members alphabetically by member\n# name. If set to NO, the members will appear in declaration order. Note that\n# this will also influence the order of the classes in the class list.\n# The default value is: NO.\n\nSORT_BRIEF_DOCS = NO\n\n# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the\n# (brief and detailed) documentation of class members so that constructors and\n# destructors are listed first. If set to NO the constructors will appear in the\n# respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.\n# Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief\n# member documentation.\n# Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting\n# detailed member documentation.\n# The default value is: NO.\n\nSORT_MEMBERS_CTORS_1ST = NO\n\n# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy\n# of group names into alphabetical order. If set to NO the group names will\n# appear in their defined order.\n# The default value is: NO.\n\nSORT_GROUP_NAMES = NO\n\n# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by\n# fully-qualified names, including namespaces. If set to NO, the class list will\n# be sorted only by class name, not including the namespace part.\n# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.\n# Note: This option applies only to the class list, not to the alphabetical\n# list.\n# The default value is: NO.\n\nSORT_BY_SCOPE_NAME = NO\n\n# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper\n# type resolution of all parameters of a function it will reject a match between\n# the prototype and the implementation of a member function even if there is\n# only one candidate or it is obvious which candidate to choose by doing a\n# simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still\n# accept a match between prototype and implementation in such cases.\n# The default value is: NO.\n\nSTRICT_PROTO_MATCHING = NO\n\n# The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo\n# list. This list is created by putting \\todo commands in the documentation.\n# The default value is: YES.\n\nGENERATE_TODOLIST = YES\n\n# The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test\n# list. This list is created by putting \\test commands in the documentation.\n# The default value is: YES.\n\nGENERATE_TESTLIST = YES\n\n# The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug\n# list. This list is created by putting \\bug commands in the documentation.\n# The default value is: YES.\n\nGENERATE_BUGLIST = YES\n\n# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO)\n# the deprecated list. This list is created by putting \\deprecated commands in\n# the documentation.\n# The default value is: YES.\n\nGENERATE_DEPRECATEDLIST= YES\n\n# The ENABLED_SECTIONS tag can be used to enable conditional documentation\n# sections, marked by \\if ... \\endif and \\cond \n# ... \\endcond blocks.\n\nENABLED_SECTIONS =\n\n# The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the\n# initial value of a variable or macro / define can have for it to appear in the\n# documentation. If the initializer consists of more lines than specified here\n# it will be hidden. Use a value of 0 to hide initializers completely. The\n# appearance of the value of individual variables and macros / defines can be\n# controlled using \\showinitializer or \\hideinitializer command in the\n# documentation regardless of this setting.\n# Minimum value: 0, maximum value: 10000, default value: 30.\n\nMAX_INITIALIZER_LINES = 30\n\n# Set the SHOW_USED_FILES tag to NO to disable the list of files generated at\n# the bottom of the documentation of classes and structs. If set to YES, the\n# list will mention the files that were used to generate the documentation.\n# The default value is: YES.\n\nSHOW_USED_FILES = YES\n\n# Set the SHOW_FILES tag to NO to disable the generation of the Files page. This\n# will remove the Files entry from the Quick Index and from the Folder Tree View\n# (if specified).\n# The default value is: YES.\n\nSHOW_FILES = YES\n\n# Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces\n# page. This will remove the Namespaces entry from the Quick Index and from the\n# Folder Tree View (if specified).\n# The default value is: YES.\n\nSHOW_NAMESPACES = YES\n\n# The FILE_VERSION_FILTER tag can be used to specify a program or script that\n# doxygen should invoke to get the current version for each file (typically from\n# the version control system). Doxygen will invoke the program by executing (via\n# popen()) the command command input-file, where command is the value of the\n# FILE_VERSION_FILTER tag, and input-file is the name of an input file provided\n# by doxygen. Whatever the program writes to standard output is used as the file\n# version. For an example see the documentation.\n\nFILE_VERSION_FILTER =\n\n# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed\n# by doxygen. The layout file controls the global structure of the generated\n# output files in an output format independent way. To create the layout file\n# that represents doxygen's defaults, run doxygen with the -l option. You can\n# optionally specify a file name after the option, if omitted DoxygenLayout.xml\n# will be used as the name of the layout file. See also section \"Changing the\n# layout of pages\" for information.\n#\n# Note that if you run doxygen from a directory containing a file called\n# DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE\n# tag is left empty.\n\nLAYOUT_FILE =\n\n# The CITE_BIB_FILES tag can be used to specify one or more bib files containing\n# the reference definitions. This must be a list of .bib files. The .bib\n# extension is automatically appended if omitted. This requires the bibtex tool\n# to be installed. See also https://en.wikipedia.org/wiki/BibTeX for more info.\n# For LaTeX the style of the bibliography can be controlled using\n# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the\n# search path. See also \\cite for info how to create references.\n\nCITE_BIB_FILES =\n\n#---------------------------------------------------------------------------\n# Configuration options related to warning and progress messages\n#---------------------------------------------------------------------------\n\n# The QUIET tag can be used to turn on/off the messages that are generated to\n# standard output by doxygen. If QUIET is set to YES this implies that the\n# messages are off.\n# The default value is: NO.\n\nQUIET = NO\n\n# The WARNINGS tag can be used to turn on/off the warning messages that are\n# generated to standard error (stderr) by doxygen. If WARNINGS is set to YES\n# this implies that the warnings are on.\n#\n# Tip: Turn warnings on while writing the documentation.\n# The default value is: YES.\n\nWARNINGS = YES\n\n# If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate\n# warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag\n# will automatically be disabled.\n# The default value is: YES.\n\nWARN_IF_UNDOCUMENTED = YES\n\n# If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for\n# potential errors in the documentation, such as documenting some parameters in\n# a documented function twice, or documenting parameters that don't exist or\n# using markup commands wrongly.\n# The default value is: YES.\n\nWARN_IF_DOC_ERROR = YES\n\n# If WARN_IF_INCOMPLETE_DOC is set to YES, doxygen will warn about incomplete\n# function parameter documentation. If set to NO, doxygen will accept that some\n# parameters have no documentation without warning.\n# The default value is: YES.\n\nWARN_IF_INCOMPLETE_DOC = YES\n\n# This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that\n# are documented, but have no documentation for their parameters or return\n# value. If set to NO, doxygen will only warn about wrong parameter\n# documentation, but not about the absence of documentation. If EXTRACT_ALL is\n# set to YES then this flag will automatically be disabled. See also\n# WARN_IF_INCOMPLETE_DOC\n# The default value is: NO.\n\nWARN_NO_PARAMDOC = NO\n\n# If WARN_IF_UNDOC_ENUM_VAL option is set to YES, doxygen will warn about\n# undocumented enumeration values. If set to NO, doxygen will accept\n# undocumented enumeration values. If EXTRACT_ALL is set to YES then this flag\n# will automatically be disabled.\n# The default value is: NO.\n\nWARN_IF_UNDOC_ENUM_VAL = NO\n\n# If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when\n# a warning is encountered. If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS\n# then doxygen will continue running as if WARN_AS_ERROR tag is set to NO, but\n# at the end of the doxygen process doxygen will return with a non-zero status.\n# If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS_PRINT then doxygen behaves\n# like FAIL_ON_WARNINGS but in case no WARN_LOGFILE is defined doxygen will not\n# write the warning messages in between other messages but write them at the end\n# of a run, in case a WARN_LOGFILE is defined the warning messages will be\n# besides being in the defined file also be shown at the end of a run, unless\n# the WARN_LOGFILE is defined as - i.e. standard output (stdout) in that case\n# the behavior will remain as with the setting FAIL_ON_WARNINGS.\n# Possible values are: NO, YES, FAIL_ON_WARNINGS and FAIL_ON_WARNINGS_PRINT.\n# The default value is: NO.\n\nWARN_AS_ERROR = NO\n\n# The WARN_FORMAT tag determines the format of the warning messages that doxygen\n# can produce. The string should contain the $file, $line, and $text tags, which\n# will be replaced by the file and line number from which the warning originated\n# and the warning text. Optionally the format may contain $version, which will\n# be replaced by the version of the file (if it could be obtained via\n# FILE_VERSION_FILTER)\n# See also: WARN_LINE_FORMAT\n# The default value is: $file:$line: $text.\n\nWARN_FORMAT = \"$file:$line: $text\"\n\n# In the $text part of the WARN_FORMAT command it is possible that a reference\n# to a more specific place is given. To make it easier to jump to this place\n# (outside of doxygen) the user can define a custom \"cut\" / \"paste\" string.\n# Example:\n# WARN_LINE_FORMAT = \"'vi $file +$line'\"\n# See also: WARN_FORMAT\n# The default value is: at line $line of file $file.\n\nWARN_LINE_FORMAT = \"at line $line of file $file\"\n\n# The WARN_LOGFILE tag can be used to specify a file to which warning and error\n# messages should be written. If left blank the output is written to standard\n# error (stderr). In case the file specified cannot be opened for writing the\n# warning and error messages are written to standard error. When as file - is\n# specified the warning and error messages are written to standard output\n# (stdout).\n\nWARN_LOGFILE =\n\n#---------------------------------------------------------------------------\n# Configuration options related to the input files\n#---------------------------------------------------------------------------\n\n# The INPUT tag is used to specify the files and/or directories that contain\n# documented source files. You may enter file names like myfile.cpp or\n# directories like /usr/src/myproject. Separate the files or directories with\n# spaces. See also FILE_PATTERNS and EXTENSION_MAPPING\n# Note: If this tag is empty the current directory is searched.\n\nINPUT = @DOXYGEN_INPUT_PATHS@\n\n# This tag can be used to specify the character encoding of the source files\n# that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses\n# libiconv (or the iconv built into libc) for the transcoding. See the libiconv\n# documentation (see:\n# https://www.gnu.org/software/libiconv/) for the list of possible encodings.\n# See also: INPUT_FILE_ENCODING\n# The default value is: UTF-8.\n\nINPUT_ENCODING = UTF-8\n\n# This tag can be used to specify the character encoding of the source files\n# that doxygen parses The INPUT_FILE_ENCODING tag can be used to specify\n# character encoding on a per file pattern basis. Doxygen will compare the file\n# name with each pattern and apply the encoding instead of the default\n# INPUT_ENCODING) if there is a match. The character encodings are a list of the\n# form: pattern=encoding (like *.php=ISO-8859-1). See cfg_input_encoding\n# \"INPUT_ENCODING\" for further information on supported encodings.\n\nINPUT_FILE_ENCODING =\n\n# If the value of the INPUT tag contains directories, you can use the\n# FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and\n# *.h) to filter out the source-files in the directories.\n#\n# Note that for custom extensions or not directly supported extensions you also\n# need to set EXTENSION_MAPPING for the extension otherwise the files are not\n# read by doxygen.\n#\n# Note the list of default checked file patterns might differ from the list of\n# default file extension mappings.\n#\n# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cxxm,\n# *.cpp, *.cppm, *.c++, *.c++m, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl,\n# *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp, *.h++, *.ixx, *.l, *.cs, *.d, *.php,\n# *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown, *.md, *.mm, *.dox (to be\n# provided as doxygen C comment), *.py, *.pyw, *.f90, *.f95, *.f03, *.f08,\n# *.f18, *.f, *.for, *.vhd, *.vhdl, *.ucf, *.qsf and *.ice.\n\nFILE_PATTERNS = *.c \\\n *.cxx \\\n *.cpp \\\n *.inl \\\n *.h \\\n *.hpp \\\n *.h++\n\n# The RECURSIVE tag can be used to specify whether or not subdirectories should\n# be searched for input files as well.\n# The default value is: NO.\n\nRECURSIVE = YES\n\n# The EXCLUDE tag can be used to specify files and/or directories that should be\n# excluded from the INPUT source files. This way you can easily exclude a\n# subdirectory from a directory tree whose root is specified with the INPUT tag.\n#\n# Note that relative paths are relative to the directory from which doxygen is\n# run.\n\nEXCLUDE =\n\n# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or\n# directories that are symbolic links (a Unix file system feature) are excluded\n# from the input.\n# The default value is: NO.\n\nEXCLUDE_SYMLINKS = NO\n\n# If the value of the INPUT tag contains directories, you can use the\n# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude\n# certain files from those directories.\n#\n# Note that the wildcards are matched against the file with absolute path, so to\n# exclude all test directories for example use the pattern */test/*\n\nEXCLUDE_PATTERNS =\n\n# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names\n# (namespaces, classes, functions, etc.) that should be excluded from the\n# output. The symbol name can be a fully qualified name, a word, or if the\n# wildcard * is used, a substring. Examples: ANamespace, AClass,\n# ANamespace::AClass, ANamespace::*Test\n\nEXCLUDE_SYMBOLS =\n\n# The EXAMPLE_PATH tag can be used to specify one or more files or directories\n# that contain example code fragments that are included (see the \\include\n# command).\n\nEXAMPLE_PATH =\n\n# If the value of the EXAMPLE_PATH tag contains directories, you can use the\n# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and\n# *.h) to filter out the source-files in the directories. If left blank all\n# files are included.\n\nEXAMPLE_PATTERNS = *\n\n# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be\n# searched for input files to be used with the \\include or \\dontinclude commands\n# irrespective of the value of the RECURSIVE tag.\n# The default value is: NO.\n\nEXAMPLE_RECURSIVE = NO\n\n# The IMAGE_PATH tag can be used to specify one or more files or directories\n# that contain images that are to be included in the documentation (see the\n# \\image command).\n\nIMAGE_PATH =\n\n# The INPUT_FILTER tag can be used to specify a program that doxygen should\n# invoke to filter for each input file. Doxygen will invoke the filter program\n# by executing (via popen()) the command:\n#\n# \n#\n# where is the value of the INPUT_FILTER tag, and is the\n# name of an input file. Doxygen will then use the output that the filter\n# program writes to standard output. If FILTER_PATTERNS is specified, this tag\n# will be ignored.\n#\n# Note that the filter must not add or remove lines; it is applied before the\n# code is scanned, but not when the output code is generated. If lines are added\n# or removed, the anchors will not be placed correctly.\n#\n# Note that doxygen will use the data processed and written to standard output\n# for further processing, therefore nothing else, like debug statements or used\n# commands (so in case of a Windows batch file always use @echo OFF), should be\n# written to standard output.\n#\n# Note that for custom extensions or not directly supported extensions you also\n# need to set EXTENSION_MAPPING for the extension otherwise the files are not\n# properly processed by doxygen.\n\nINPUT_FILTER =\n\n# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern\n# basis. Doxygen will compare the file name with each pattern and apply the\n# filter if there is a match. The filters are a list of the form: pattern=filter\n# (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how\n# filters are used. If the FILTER_PATTERNS tag is empty or if none of the\n# patterns match the file name, INPUT_FILTER is applied.\n#\n# Note that for custom extensions or not directly supported extensions you also\n# need to set EXTENSION_MAPPING for the extension otherwise the files are not\n# properly processed by doxygen.\n\nFILTER_PATTERNS =\n\n# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using\n# INPUT_FILTER) will also be used to filter the input files that are used for\n# producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).\n# The default value is: NO.\n\nFILTER_SOURCE_FILES = NO\n\n# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file\n# pattern. A pattern will override the setting for FILTER_PATTERN (if any) and\n# it is also possible to disable source filtering for a specific pattern using\n# *.ext= (so without naming a filter).\n# This tag requires that the tag FILTER_SOURCE_FILES is set to YES.\n\nFILTER_SOURCE_PATTERNS =\n\n# If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that\n# is part of the input, its contents will be placed on the main page\n# (index.html). This can be useful if you have a project on for instance GitHub\n# and want to reuse the introduction page also for the doxygen output.\n\nUSE_MDFILE_AS_MAINPAGE =\n\n# The Fortran standard specifies that for fixed formatted Fortran code all\n# characters from position 72 are to be considered as comment. A common\n# extension is to allow longer lines before the automatic comment starts. The\n# setting FORTRAN_COMMENT_AFTER will also make it possible that longer lines can\n# be processed before the automatic comment starts.\n# Minimum value: 7, maximum value: 10000, default value: 72.\n\nFORTRAN_COMMENT_AFTER = 72\n\n#---------------------------------------------------------------------------\n# Configuration options related to source browsing\n#---------------------------------------------------------------------------\n\n# If the SOURCE_BROWSER tag is set to YES then a list of source files will be\n# generated. Documented entities will be cross-referenced with these sources.\n#\n# Note: To get rid of all source code in the generated output, make sure that\n# also VERBATIM_HEADERS is set to NO.\n# The default value is: NO.\n\nSOURCE_BROWSER = NO\n\n# Setting the INLINE_SOURCES tag to YES will include the body of functions,\n# classes and enums directly into the documentation.\n# The default value is: NO.\n\nINLINE_SOURCES = NO\n\n# Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any\n# special comment blocks from generated source code fragments. Normal C, C++ and\n# Fortran comments will always remain visible.\n# The default value is: YES.\n\nSTRIP_CODE_COMMENTS = YES\n\n# If the REFERENCED_BY_RELATION tag is set to YES then for each documented\n# entity all documented functions referencing it will be listed.\n# The default value is: NO.\n\nREFERENCED_BY_RELATION = NO\n\n# If the REFERENCES_RELATION tag is set to YES then for each documented function\n# all documented entities called/used by that function will be listed.\n# The default value is: NO.\n\nREFERENCES_RELATION = NO\n\n# If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set\n# to YES then the hyperlinks from functions in REFERENCES_RELATION and\n# REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will\n# link to the documentation.\n# The default value is: YES.\n\nREFERENCES_LINK_SOURCE = YES\n\n# If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the\n# source code will show a tooltip with additional information such as prototype,\n# brief description and links to the definition and documentation. Since this\n# will make the HTML file larger and loading of large files a bit slower, you\n# can opt to disable this feature.\n# The default value is: YES.\n# This tag requires that the tag SOURCE_BROWSER is set to YES.\n\nSOURCE_TOOLTIPS = YES\n\n# If the USE_HTAGS tag is set to YES then the references to source code will\n# point to the HTML generated by the htags(1) tool instead of doxygen built-in\n# source browser. The htags tool is part of GNU's global source tagging system\n# (see https://www.gnu.org/software/global/global.html). You will need version\n# 4.8.6 or higher.\n#\n# To use it do the following:\n# - Install the latest version of global\n# - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file\n# - Make sure the INPUT points to the root of the source tree\n# - Run doxygen as normal\n#\n# Doxygen will invoke htags (and that will in turn invoke gtags), so these\n# tools must be available from the command line (i.e. in the search path).\n#\n# The result: instead of the source browser generated by doxygen, the links to\n# source code will now point to the output of htags.\n# The default value is: NO.\n# This tag requires that the tag SOURCE_BROWSER is set to YES.\n\nUSE_HTAGS = NO\n\n# If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a\n# verbatim copy of the header file for each class for which an include is\n# specified. Set to NO to disable this.\n# See also: Section \\class.\n# The default value is: YES.\n\nVERBATIM_HEADERS = YES\n\n# If the CLANG_ASSISTED_PARSING tag is set to YES then doxygen will use the\n# clang parser (see:\n# http://clang.llvm.org/) for more accurate parsing at the cost of reduced\n# performance. This can be particularly helpful with template rich C++ code for\n# which doxygen's built-in parser lacks the necessary type information.\n# Note: The availability of this option depends on whether or not doxygen was\n# generated with the -Duse_libclang=ON option for CMake.\n# The default value is: NO.\n\nCLANG_ASSISTED_PARSING = NO\n\n# If the CLANG_ASSISTED_PARSING tag is set to YES and the CLANG_ADD_INC_PATHS\n# tag is set to YES then doxygen will add the directory of each input to the\n# include path.\n# The default value is: YES.\n# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.\n\nCLANG_ADD_INC_PATHS = YES\n\n# If clang assisted parsing is enabled you can provide the compiler with command\n# line options that you would normally use when invoking the compiler. Note that\n# the include paths will already be set by doxygen for the files and directories\n# specified with INPUT and INCLUDE_PATH.\n# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.\n\nCLANG_OPTIONS =\n\n# If clang assisted parsing is enabled you can provide the clang parser with the\n# path to the directory containing a file called compile_commands.json. This\n# file is the compilation database (see:\n# http://clang.llvm.org/docs/HowToSetupToolingForLLVM.html) containing the\n# options used when the source files were built. This is equivalent to\n# specifying the -p option to a clang tool, such as clang-check. These options\n# will then be passed to the parser. Any options specified with CLANG_OPTIONS\n# will be added as well.\n# Note: The availability of this option depends on whether or not doxygen was\n# generated with the -Duse_libclang=ON option for CMake.\n\nCLANG_DATABASE_PATH =\n\n#---------------------------------------------------------------------------\n# Configuration options related to the alphabetical class index\n#---------------------------------------------------------------------------\n\n# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all\n# compounds will be generated. Enable this if the project contains a lot of\n# classes, structs, unions or interfaces.\n# The default value is: YES.\n\nALPHABETICAL_INDEX = YES\n\n# The IGNORE_PREFIX tag can be used to specify a prefix (or a list of prefixes)\n# that should be ignored while generating the index headers. The IGNORE_PREFIX\n# tag works for classes, function and member names. The entity will be placed in\n# the alphabetical list under the first letter of the entity name that remains\n# after removing the prefix.\n# This tag requires that the tag ALPHABETICAL_INDEX is set to YES.\n\nIGNORE_PREFIX =\n\n#---------------------------------------------------------------------------\n# Configuration options related to the HTML output\n#---------------------------------------------------------------------------\n\n# If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output\n# The default value is: YES.\n\nGENERATE_HTML = NO\n\n# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a\n# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of\n# it.\n# The default directory is: html.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_OUTPUT = html\n\n# The HTML_FILE_EXTENSION tag can be used to specify the file extension for each\n# generated HTML page (for example: .htm, .php, .asp).\n# The default value is: .html.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_FILE_EXTENSION = .html\n\n# The HTML_HEADER tag can be used to specify a user-defined HTML header file for\n# each generated HTML page. If the tag is left blank doxygen will generate a\n# standard header.\n#\n# To get valid HTML the header file that includes any scripts and style sheets\n# that doxygen needs, which is dependent on the configuration options used (e.g.\n# the setting GENERATE_TREEVIEW). It is highly recommended to start with a\n# default header using\n# doxygen -w html new_header.html new_footer.html new_stylesheet.css\n# YourConfigFile\n# and then modify the file new_header.html. See also section \"Doxygen usage\"\n# for information on how to generate the default header that doxygen normally\n# uses.\n# Note: The header is subject to change so you typically have to regenerate the\n# default header when upgrading to a newer version of doxygen. For a description\n# of the possible markers and block names see the documentation.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_HEADER =\n\n# The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each\n# generated HTML page. If the tag is left blank doxygen will generate a standard\n# footer. See HTML_HEADER for more information on how to generate a default\n# footer and what special commands can be used inside the footer. See also\n# section \"Doxygen usage\" for information on how to generate the default footer\n# that doxygen normally uses.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_FOOTER =\n\n# The HTML_STYLESHEET tag can be used to specify a user-defined cascading style\n# sheet that is used by each HTML page. It can be used to fine-tune the look of\n# the HTML output. If left blank doxygen will generate a default style sheet.\n# See also section \"Doxygen usage\" for information on how to generate the style\n# sheet that doxygen normally uses.\n# Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as\n# it is more robust and this tag (HTML_STYLESHEET) will in the future become\n# obsolete.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_STYLESHEET =\n\n# The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined\n# cascading style sheets that are included after the standard style sheets\n# created by doxygen. Using this option one can overrule certain style aspects.\n# This is preferred over using HTML_STYLESHEET since it does not replace the\n# standard style sheet and is therefore more robust against future updates.\n# Doxygen will copy the style sheet files to the output directory.\n# Note: The order of the extra style sheet files is of importance (e.g. the last\n# style sheet in the list overrules the setting of the previous ones in the\n# list).\n# Note: Since the styling of scrollbars can currently not be overruled in\n# Webkit/Chromium, the styling will be left out of the default doxygen.css if\n# one or more extra stylesheets have been specified. So if scrollbar\n# customization is desired it has to be added explicitly. For an example see the\n# documentation.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_EXTRA_STYLESHEET =\n\n# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or\n# other source files which should be copied to the HTML output directory. Note\n# that these files will be copied to the base HTML output directory. Use the\n# $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these\n# files. In the HTML_STYLESHEET file, use the file name only. Also note that the\n# files will be copied as-is; there are no commands or markers available.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_EXTRA_FILES =\n\n# The HTML_COLORSTYLE tag can be used to specify if the generated HTML output\n# should be rendered with a dark or light theme.\n# Possible values are: LIGHT always generate light mode output, DARK always\n# generate dark mode output, AUTO_LIGHT automatically set the mode according to\n# the user preference, use light mode if no preference is set (the default),\n# AUTO_DARK automatically set the mode according to the user preference, use\n# dark mode if no preference is set and TOGGLE allow to user to switch between\n# light and dark mode via a button.\n# The default value is: AUTO_LIGHT.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_COLORSTYLE = AUTO_LIGHT\n\n# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen\n# will adjust the colors in the style sheet and background images according to\n# this color. Hue is specified as an angle on a color-wheel, see\n# https://en.wikipedia.org/wiki/Hue for more information. For instance the value\n# 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300\n# purple, and 360 is red again.\n# Minimum value: 0, maximum value: 359, default value: 220.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_COLORSTYLE_HUE = 220\n\n# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors\n# in the HTML output. For a value of 0 the output will use gray-scales only. A\n# value of 255 will produce the most vivid colors.\n# Minimum value: 0, maximum value: 255, default value: 100.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_COLORSTYLE_SAT = 100\n\n# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the\n# luminance component of the colors in the HTML output. Values below 100\n# gradually make the output lighter, whereas values above 100 make the output\n# darker. The value divided by 100 is the actual gamma applied, so 80 represents\n# a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not\n# change the gamma.\n# Minimum value: 40, maximum value: 240, default value: 80.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_COLORSTYLE_GAMMA = 80\n\n# If the HTML_DYNAMIC_MENUS tag is set to YES then the generated HTML\n# documentation will contain a main index with vertical navigation menus that\n# are dynamically created via JavaScript. If disabled, the navigation index will\n# consists of multiple levels of tabs that are statically embedded in every HTML\n# page. Disable this option to support browsers that do not have JavaScript,\n# like the Qt help browser.\n# The default value is: YES.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_DYNAMIC_MENUS = YES\n\n# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML\n# documentation will contain sections that can be hidden and shown after the\n# page has loaded.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_DYNAMIC_SECTIONS = NO\n\n# If the HTML_CODE_FOLDING tag is set to YES then classes and functions can be\n# dynamically folded and expanded in the generated HTML source code.\n# The default value is: YES.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_CODE_FOLDING = YES\n\n# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries\n# shown in the various tree structured indices initially; the user can expand\n# and collapse entries dynamically later on. Doxygen will expand the tree to\n# such a level that at most the specified number of entries are visible (unless\n# a fully collapsed tree already exceeds this amount). So setting the number of\n# entries 1 will produce a full collapsed tree by default. 0 is a special value\n# representing an infinite number of entries and will result in a full expanded\n# tree by default.\n# Minimum value: 0, maximum value: 9999, default value: 100.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_INDEX_NUM_ENTRIES = 100\n\n# If the GENERATE_DOCSET tag is set to YES, additional index files will be\n# generated that can be used as input for Apple's Xcode 3 integrated development\n# environment (see:\n# https://developer.apple.com/xcode/), introduced with OSX 10.5 (Leopard). To\n# create a documentation set, doxygen will generate a Makefile in the HTML\n# output directory. Running make will produce the docset in that directory and\n# running make install will install the docset in\n# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at\n# startup. See https://developer.apple.com/library/archive/featuredarticles/Doxy\n# genXcode/_index.html for more information.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nGENERATE_DOCSET = NO\n\n# This tag determines the name of the docset feed. A documentation feed provides\n# an umbrella under which multiple documentation sets from a single provider\n# (such as a company or product suite) can be grouped.\n# The default value is: Doxygen generated docs.\n# This tag requires that the tag GENERATE_DOCSET is set to YES.\n\nDOCSET_FEEDNAME = \"Doxygen generated docs\"\n\n# This tag determines the URL of the docset feed. A documentation feed provides\n# an umbrella under which multiple documentation sets from a single provider\n# (such as a company or product suite) can be grouped.\n# This tag requires that the tag GENERATE_DOCSET is set to YES.\n\nDOCSET_FEEDURL =\n\n# This tag specifies a string that should uniquely identify the documentation\n# set bundle. This should be a reverse domain-name style string, e.g.\n# com.mycompany.MyDocSet. Doxygen will append .docset to the name.\n# The default value is: org.doxygen.Project.\n# This tag requires that the tag GENERATE_DOCSET is set to YES.\n\nDOCSET_BUNDLE_ID = org.doxygen.Project\n\n# The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify\n# the documentation publisher. This should be a reverse domain-name style\n# string, e.g. com.mycompany.MyDocSet.documentation.\n# The default value is: org.doxygen.Publisher.\n# This tag requires that the tag GENERATE_DOCSET is set to YES.\n\nDOCSET_PUBLISHER_ID = org.doxygen.Publisher\n\n# The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.\n# The default value is: Publisher.\n# This tag requires that the tag GENERATE_DOCSET is set to YES.\n\nDOCSET_PUBLISHER_NAME = Publisher\n\n# If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three\n# additional HTML index files: index.hhp, index.hhc, and index.hhk. The\n# index.hhp is a project file that can be read by Microsoft's HTML Help Workshop\n# on Windows. In the beginning of 2021 Microsoft took the original page, with\n# a.o. the download links, offline the HTML help workshop was already many years\n# in maintenance mode). You can download the HTML help workshop from the web\n# archives at Installation executable (see:\n# http://web.archive.org/web/20160201063255/http://download.microsoft.com/downlo\n# ad/0/A/9/0A939EF6-E31C-430F-A3DF-DFAE7960D564/htmlhelp.exe).\n#\n# The HTML Help Workshop contains a compiler that can convert all HTML output\n# generated by doxygen into a single compiled HTML file (.chm). Compiled HTML\n# files are now used as the Windows 98 help format, and will replace the old\n# Windows help format (.hlp) on all Windows platforms in the future. Compressed\n# HTML files also contain an index, a table of contents, and you can search for\n# words in the documentation. The HTML workshop also contains a viewer for\n# compressed HTML files.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nGENERATE_HTMLHELP = NO\n\n# The CHM_FILE tag can be used to specify the file name of the resulting .chm\n# file. You can add a path in front of the file if the result should not be\n# written to the html output directory.\n# This tag requires that the tag GENERATE_HTMLHELP is set to YES.\n\nCHM_FILE =\n\n# The HHC_LOCATION tag can be used to specify the location (absolute path\n# including file name) of the HTML help compiler (hhc.exe). If non-empty,\n# doxygen will try to run the HTML help compiler on the generated index.hhp.\n# The file has to be specified with full path.\n# This tag requires that the tag GENERATE_HTMLHELP is set to YES.\n\nHHC_LOCATION =\n\n# The GENERATE_CHI flag controls if a separate .chi index file is generated\n# (YES) or that it should be included in the main .chm file (NO).\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTMLHELP is set to YES.\n\nGENERATE_CHI = NO\n\n# The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc)\n# and project file content.\n# This tag requires that the tag GENERATE_HTMLHELP is set to YES.\n\nCHM_INDEX_ENCODING =\n\n# The BINARY_TOC flag controls whether a binary table of contents is generated\n# (YES) or a normal table of contents (NO) in the .chm file. Furthermore it\n# enables the Previous and Next buttons.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTMLHELP is set to YES.\n\nBINARY_TOC = NO\n\n# The TOC_EXPAND flag can be set to YES to add extra items for group members to\n# the table of contents of the HTML help documentation and to the tree view.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTMLHELP is set to YES.\n\nTOC_EXPAND = NO\n\n# The SITEMAP_URL tag is used to specify the full URL of the place where the\n# generated documentation will be placed on the server by the user during the\n# deployment of the documentation. The generated sitemap is called sitemap.xml\n# and placed on the directory specified by HTML_OUTPUT. In case no SITEMAP_URL\n# is specified no sitemap is generated. For information about the sitemap\n# protocol see https://www.sitemaps.org\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nSITEMAP_URL =\n\n# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and\n# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that\n# can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help\n# (.qch) of the generated HTML documentation.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nGENERATE_QHP = NO\n\n# If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify\n# the file name of the resulting .qch file. The path specified is relative to\n# the HTML output folder.\n# This tag requires that the tag GENERATE_QHP is set to YES.\n\nQCH_FILE =\n\n# The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help\n# Project output. For more information please see Qt Help Project / Namespace\n# (see:\n# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace).\n# The default value is: org.doxygen.Project.\n# This tag requires that the tag GENERATE_QHP is set to YES.\n\nQHP_NAMESPACE = org.doxygen.Project\n\n# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt\n# Help Project output. For more information please see Qt Help Project / Virtual\n# Folders (see:\n# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-folders).\n# The default value is: doc.\n# This tag requires that the tag GENERATE_QHP is set to YES.\n\nQHP_VIRTUAL_FOLDER = doc\n\n# If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom\n# filter to add. For more information please see Qt Help Project / Custom\n# Filters (see:\n# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).\n# This tag requires that the tag GENERATE_QHP is set to YES.\n\nQHP_CUST_FILTER_NAME =\n\n# The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the\n# custom filter to add. For more information please see Qt Help Project / Custom\n# Filters (see:\n# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).\n# This tag requires that the tag GENERATE_QHP is set to YES.\n\nQHP_CUST_FILTER_ATTRS =\n\n# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this\n# project's filter section matches. Qt Help Project / Filter Attributes (see:\n# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes).\n# This tag requires that the tag GENERATE_QHP is set to YES.\n\nQHP_SECT_FILTER_ATTRS =\n\n# The QHG_LOCATION tag can be used to specify the location (absolute path\n# including file name) of Qt's qhelpgenerator. If non-empty doxygen will try to\n# run qhelpgenerator on the generated .qhp file.\n# This tag requires that the tag GENERATE_QHP is set to YES.\n\nQHG_LOCATION =\n\n# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be\n# generated, together with the HTML files, they form an Eclipse help plugin. To\n# install this plugin and make it available under the help contents menu in\n# Eclipse, the contents of the directory containing the HTML and XML files needs\n# to be copied into the plugins directory of eclipse. The name of the directory\n# within the plugins directory should be the same as the ECLIPSE_DOC_ID value.\n# After copying Eclipse needs to be restarted before the help appears.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nGENERATE_ECLIPSEHELP = NO\n\n# A unique identifier for the Eclipse help plugin. When installing the plugin\n# the directory name containing the HTML and XML files should also have this\n# name. Each documentation set should have its own identifier.\n# The default value is: org.doxygen.Project.\n# This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.\n\nECLIPSE_DOC_ID = org.doxygen.Project\n\n# If you want full control over the layout of the generated HTML pages it might\n# be necessary to disable the index and replace it with your own. The\n# DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top\n# of each HTML page. A value of NO enables the index and the value YES disables\n# it. Since the tabs in the index contain the same information as the navigation\n# tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nDISABLE_INDEX = NO\n\n# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index\n# structure should be generated to display hierarchical information. If the tag\n# value is set to YES, a side panel will be generated containing a tree-like\n# index structure (just like the one that is generated for HTML Help). For this\n# to work a browser that supports JavaScript, DHTML, CSS and frames is required\n# (i.e. any modern browser). Windows users are probably better off using the\n# HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can\n# further fine tune the look of the index (see \"Fine-tuning the output\"). As an\n# example, the default style sheet generated by doxygen has an example that\n# shows how to put an image at the root of the tree instead of the PROJECT_NAME.\n# Since the tree basically has the same information as the tab index, you could\n# consider setting DISABLE_INDEX to YES when enabling this option.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nGENERATE_TREEVIEW = YES\n\n# When both GENERATE_TREEVIEW and DISABLE_INDEX are set to YES, then the\n# FULL_SIDEBAR option determines if the side bar is limited to only the treeview\n# area (value NO) or if it should extend to the full height of the window (value\n# YES). Setting this to YES gives a layout similar to\n# https://docs.readthedocs.io with more room for contents, but less room for the\n# project logo, title, and description. If either GENERATE_TREEVIEW or\n# DISABLE_INDEX is set to NO, this option has no effect.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nFULL_SIDEBAR = NO\n\n# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that\n# doxygen will group on one line in the generated HTML documentation.\n#\n# Note that a value of 0 will completely suppress the enum values from appearing\n# in the overview section.\n# Minimum value: 0, maximum value: 20, default value: 4.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nENUM_VALUES_PER_LINE = 4\n\n# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used\n# to set the initial width (in pixels) of the frame in which the tree is shown.\n# Minimum value: 0, maximum value: 1500, default value: 250.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nTREEVIEW_WIDTH = 250\n\n# If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to\n# external symbols imported via tag files in a separate window.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nEXT_LINKS_IN_WINDOW = NO\n\n# If the OBFUSCATE_EMAILS tag is set to YES, doxygen will obfuscate email\n# addresses.\n# The default value is: YES.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nOBFUSCATE_EMAILS = YES\n\n# If the HTML_FORMULA_FORMAT option is set to svg, doxygen will use the pdf2svg\n# tool (see https://github.com/dawbarton/pdf2svg) or inkscape (see\n# https://inkscape.org) to generate formulas as SVG images instead of PNGs for\n# the HTML output. These images will generally look nicer at scaled resolutions.\n# Possible values are: png (the default) and svg (looks nicer but requires the\n# pdf2svg or inkscape tool).\n# The default value is: png.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_FORMULA_FORMAT = png\n\n# Use this tag to change the font size of LaTeX formulas included as images in\n# the HTML documentation. When you change the font size after a successful\n# doxygen run you need to manually remove any form_*.png images from the HTML\n# output directory to force them to be regenerated.\n# Minimum value: 8, maximum value: 50, default value: 10.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nFORMULA_FONTSIZE = 10\n\n# The FORMULA_MACROFILE can contain LaTeX \\newcommand and \\renewcommand commands\n# to create new LaTeX commands to be used in formulas as building blocks. See\n# the section \"Including formulas\" for details.\n\nFORMULA_MACROFILE =\n\n# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see\n# https://www.mathjax.org) which uses client side JavaScript for the rendering\n# instead of using pre-rendered bitmaps. Use this if you do not have LaTeX\n# installed or if you want to formulas look prettier in the HTML output. When\n# enabled you may also need to install MathJax separately and configure the path\n# to it using the MATHJAX_RELPATH option.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nUSE_MATHJAX = NO\n\n# With MATHJAX_VERSION it is possible to specify the MathJax version to be used.\n# Note that the different versions of MathJax have different requirements with\n# regards to the different settings, so it is possible that also other MathJax\n# settings have to be changed when switching between the different MathJax\n# versions.\n# Possible values are: MathJax_2 and MathJax_3.\n# The default value is: MathJax_2.\n# This tag requires that the tag USE_MATHJAX is set to YES.\n\nMATHJAX_VERSION = MathJax_2\n\n# When MathJax is enabled you can set the default output format to be used for\n# the MathJax output. For more details about the output format see MathJax\n# version 2 (see:\n# http://docs.mathjax.org/en/v2.7-latest/output.html) and MathJax version 3\n# (see:\n# http://docs.mathjax.org/en/latest/web/components/output.html).\n# Possible values are: HTML-CSS (which is slower, but has the best\n# compatibility. This is the name for Mathjax version 2, for MathJax version 3\n# this will be translated into chtml), NativeMML (i.e. MathML. Only supported\n# for NathJax 2. For MathJax version 3 chtml will be used instead.), chtml (This\n# is the name for Mathjax version 3, for MathJax version 2 this will be\n# translated into HTML-CSS) and SVG.\n# The default value is: HTML-CSS.\n# This tag requires that the tag USE_MATHJAX is set to YES.\n\nMATHJAX_FORMAT = HTML-CSS\n\n# When MathJax is enabled you need to specify the location relative to the HTML\n# output directory using the MATHJAX_RELPATH option. The destination directory\n# should contain the MathJax.js script. For instance, if the mathjax directory\n# is located at the same level as the HTML output directory, then\n# MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax\n# Content Delivery Network so you can quickly see the result without installing\n# MathJax. However, it is strongly recommended to install a local copy of\n# MathJax from https://www.mathjax.org before deployment. The default value is:\n# - in case of MathJax version 2: https://cdn.jsdelivr.net/npm/mathjax@2\n# - in case of MathJax version 3: https://cdn.jsdelivr.net/npm/mathjax@3\n# This tag requires that the tag USE_MATHJAX is set to YES.\n\nMATHJAX_RELPATH =\n\n# The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax\n# extension names that should be enabled during MathJax rendering. For example\n# for MathJax version 2 (see\n# https://docs.mathjax.org/en/v2.7-latest/tex.html#tex-and-latex-extensions):\n# MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols\n# For example for MathJax version 3 (see\n# http://docs.mathjax.org/en/latest/input/tex/extensions/index.html):\n# MATHJAX_EXTENSIONS = ams\n# This tag requires that the tag USE_MATHJAX is set to YES.\n\nMATHJAX_EXTENSIONS =\n\n# The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces\n# of code that will be used on startup of the MathJax code. See the MathJax site\n# (see:\n# http://docs.mathjax.org/en/v2.7-latest/output.html) for more details. For an\n# example see the documentation.\n# This tag requires that the tag USE_MATHJAX is set to YES.\n\nMATHJAX_CODEFILE =\n\n# When the SEARCHENGINE tag is enabled doxygen will generate a search box for\n# the HTML output. The underlying search engine uses javascript and DHTML and\n# should work on any modern browser. Note that when using HTML help\n# (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)\n# there is already a search function so this one should typically be disabled.\n# For large projects the javascript based search engine can be slow, then\n# enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to\n# search using the keyboard; to jump to the search box use + S\n# (what the is depends on the OS and browser, but it is typically\n# , /