Update to ETL 20.41.1 #2
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…thub.com/ETLCPP/etl into feature/ETLCPP#757-Add-time-date-classes
…thub.com/ETLCPP/etl into feature/ETLCPP#757-Add-time-date-classes
…thub.com/ETLCPP/etl into feature/ETLCPP#757-Add-time-date-classes
…thub.com/ETLCPP/etl into feature/ETLCPP#757-Add-time-date-classes
…thub.com/ETLCPP/etl into feature/ETLCPP#757-Add-time-date-classes
…thub.com/ETLCPP/etl into feature/ETLCPP#757-Add-time-date-classes
…thub.com/ETLCPP/etl into feature/ETLCPP#757-Add-time-date-classes
…thub.com/ETLCPP/etl into feature/ETLCPP#757-Add-time-date-classes
…thub.com/ETLCPP/etl into feature/ETLCPP#757-Add-time-date-classes
…thub.com/ETLCPP/etl into feature/ETLCPP#757-Add-time-date-classes
…thub.com/ETLCPP/etl into feature/ETLCPP#757-Add-time-date-classes # Conflicts: # include/etl/chrono.h # include/etl/private/chrono/day.h # include/etl/private/chrono/duration.h # test/CMakeLists.txt # test/test_chrono_day.cpp # test/vs2022/etl.vcxproj # test/vs2022/etl.vcxproj.filters
…thub.com/ETLCPP/etl-21 into dual-licence/feature/ETLCPP#757-Add-time-date-classes
…thub.com/ETLCPP/etl-21 into dual-licence/feature/ETLCPP#757-Add-time-date-classes # Conflicts: # include/etl/chrono.h # include/etl/private/chrono/day.h # include/etl/private/chrono/duration.h # test/CMakeLists.txt # test/test_chrono_day.cpp # test/vs2022/etl.vcxproj # test/vs2022/etl.vcxproj.filters
…usive link utilities
* Add Zephyr build system module.yml (ETLCPP#1074) The Zephyr build system requires that modules have a `module.yml` file to specify where the module cmake and kconfig files are located. These can also be explicitly set as "external" meaning that they do not exist within the module tree, itself. These build file can still be specified elsewhere via cmake variables, explained more in-depth here: https://docs.zephyrproject.org/latest/develop/modules.html#modules-module-ext-root This change makes it such that ETL can be included more easily in zephyr projects running on embedded systems. A similar change can be observed in the public nanopb repository, where the repo only requires its own `zephyr/module.yml` file to be found by the zephyr build system, but the kconfig and cmake additions can exist outside of the library repository. * Add full West support for ETL (ETLCPP#1075) This will allow ETL to be included via west in a zephyr build without any additional wrappers or external kconfigs. Signed-off-by: Zach Van Camp <zach.vancamp@etcconnect.com> Co-authored-by: Zach Van Camp <zach.vancamp@etcconnect.com> * refactor: use etl::clamp for clamping the set value --------- Signed-off-by: Zach Van Camp <zach.vancamp@etcconnect.com> Co-authored-by: Zach Van Camp <marshmilo100@gmail.com> Co-authored-by: Zach Van Camp <zach.vancamp@etcconnect.com> Co-authored-by: John Wellbelove <jwellbelove@users.noreply.github.com>
…lopment # Conflicts: # include/etl/cyclic_value.h
…LCPP#1103) * Add Zephyr build system module.yml (ETLCPP#1074) The Zephyr build system requires that modules have a `module.yml` file to specify where the module cmake and kconfig files are located. These can also be explicitly set as "external" meaning that they do not exist within the module tree, itself. These build file can still be specified elsewhere via cmake variables, explained more in-depth here: https://docs.zephyrproject.org/latest/develop/modules.html#modules-module-ext-root This change makes it such that ETL can be included more easily in zephyr projects running on embedded systems. A similar change can be observed in the public nanopb repository, where the repo only requires its own `zephyr/module.yml` file to be found by the zephyr build system, but the kconfig and cmake additions can exist outside of the library repository. * Add full West support for ETL (ETLCPP#1075) This will allow ETL to be included via west in a zephyr build without any additional wrappers or external kconfigs. Signed-off-by: Zach Van Camp <zach.vancamp@etcconnect.com> Co-authored-by: Zach Van Camp <zach.vancamp@etcconnect.com> * Add IWYU pragmas to private headers which provide library symbols This prevents warnings in clang compiler and IWYU tool https://clangd.llvm.org/guides/include-cleaner#iwyu-pragmas https://github.com/include-what-you-use/include-what-you-use/blob/master/docs/IWYUPragmas.md#iwyu-pragma-export --------- Signed-off-by: Zach Van Camp <zach.vancamp@etcconnect.com> Co-authored-by: Zach Van Camp <marshmilo100@gmail.com> Co-authored-by: Zach Van Camp <zach.vancamp@etcconnect.com> Co-authored-by: John Wellbelove <jwellbelove@users.noreply.github.com>
…LCPP#1103) * Add Zephyr build system module.yml (ETLCPP#1074) The Zephyr build system requires that modules have a `module.yml` file to specify where the module cmake and kconfig files are located. These can also be explicitly set as "external" meaning that they do not exist within the module tree, itself. These build file can still be specified elsewhere via cmake variables, explained more in-depth here: https://docs.zephyrproject.org/latest/develop/modules.html#modules-module-ext-root This change makes it such that ETL can be included more easily in zephyr projects running on embedded systems. A similar change can be observed in the public nanopb repository, where the repo only requires its own `zephyr/module.yml` file to be found by the zephyr build system, but the kconfig and cmake additions can exist outside of the library repository. * Add full West support for ETL (ETLCPP#1075) This will allow ETL to be included via west in a zephyr build without any additional wrappers or external kconfigs. Signed-off-by: Zach Van Camp <zach.vancamp@etcconnect.com> Co-authored-by: Zach Van Camp <zach.vancamp@etcconnect.com> * Add IWYU pragmas to private headers which provide library symbols This prevents warnings in clang compiler and IWYU tool https://clangd.llvm.org/guides/include-cleaner#iwyu-pragmas https://github.com/include-what-you-use/include-what-you-use/blob/master/docs/IWYUPragmas.md#iwyu-pragma-export --------- Signed-off-by: Zach Van Camp <zach.vancamp@etcconnect.com> Co-authored-by: Zach Van Camp <marshmilo100@gmail.com> Co-authored-by: Zach Van Camp <zach.vancamp@etcconnect.com> Co-authored-by: John Wellbelove <jwellbelove@users.noreply.github.com>
# Conflicts: # zephyr/module.yml
* Add clang devcontainers * Add gcc devcontainers * Remove comment * Transition to bullseye variants of clang image to build --------- Co-authored-by: John Wellbelove <jwellbelove@users.noreply.github.com>
Author
|
Merge conflict caused by rebasing the openbsw-replace-estd branch. Can master also be rebased to upstream etl before merge? |
Added missing comparison operators Replaced 'typedef' with 'using'
Co-authored-by: John Wellbelove <jwellbelove@users.noreply.github.com>
rolandreichweinbmw
force-pushed
the
openbsw-replace-estd
branch
from
802f01f to
83433ae
Compare
Author
|
Now, the only deviation is the additional Function Wrapper etl::inplace_function, which is not yet part of the released ETL (but hopefully, soon). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
14 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Only deviations we still have: