OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/lib/posix/options/Kconfig.compat

19 lines
443 B
Plaintext
Raw Normal View History

posix: split supported features into separate Kconfig files This change is setting up for switching over to proper POSIX option requirements, feature test macros, and a dependency structure that is reflective of the standard. Signed-off-by: Christopher Friedt <cfriedt@meta.com>
2023-07-04 03:15:35 +08:00
# Copyright (c) 2020 Tobias Svehagen
# Copyright (c) 2023 Meta
#
# SPDX-License-Identifier: Apache-2.0
posix: relocate Kconfig.eventfd to Kconfig.compat While event file descriptors (eventfd) are extremely useful, the API has still not been formalized as part of the POSIX specification. Therefore, move this to a separate Kconfig menu for "compat" (compatibility) features. Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
2024-05-24 00:19:58 +08:00
menu "Miscellaneous POSIX-related options"
posix: eventfd: fix dependency cycle between net and posix Until recently, the posix api was purely a consumer of the network subsystem. However, a dependency cycle was added as a stop-gap solution for challenges with the native platform. Specifically, 1. eventfd symbols conflict with those of the host 2. eventfd was excluded from native libc builds via cmake If any part of the posix were then to select the network subsystem (which is a legitimate use case, given that networking is a part of the posix api), we would get a build error due to the Kconfig dependency cycle. As usual, with dependency cycles, the cycle can be broken via a third, mutual dependency. What is the third mutual dependency? Naturally, it is ZVFS which was planned some time ago. ZVFS will be where we collect file-descriptor and FILE-pointer APIs so that we can ensure consistency for Zephyr users. This change deprecates EVENTFD_MAX in favour of ZVFS_EVENTFD_MAX. Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
2024-05-29 07:39:06 +08:00
config EVENTFD
posix: split supported features into separate Kconfig files This change is setting up for switching over to proper POSIX option requirements, feature test macros, and a dependency structure that is reflective of the standard. Signed-off-by: Christopher Friedt <cfriedt@meta.com>
2023-07-04 03:15:35 +08:00
bool "Support for eventfd"
depends on !NATIVE_APPLICATION
posix: eventfd: fix dependency cycle between net and posix Until recently, the posix api was purely a consumer of the network subsystem. However, a dependency cycle was added as a stop-gap solution for challenges with the native platform. Specifically, 1. eventfd symbols conflict with those of the host 2. eventfd was excluded from native libc builds via cmake If any part of the posix were then to select the network subsystem (which is a legitimate use case, given that networking is a part of the posix api), we would get a build error due to the Kconfig dependency cycle. As usual, with dependency cycles, the cycle can be broken via a third, mutual dependency. What is the third mutual dependency? Naturally, it is ZVFS which was planned some time ago. ZVFS will be where we collect file-descriptor and FILE-pointer APIs so that we can ensure consistency for Zephyr users. This change deprecates EVENTFD_MAX in favour of ZVFS_EVENTFD_MAX. Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
2024-05-29 07:39:06 +08:00
select ZVFS
select ZVFS_EVENTFD
posix: split supported features into separate Kconfig files This change is setting up for switching over to proper POSIX option requirements, feature test macros, and a dependency structure that is reflective of the standard. Signed-off-by: Christopher Friedt <cfriedt@meta.com>
2023-07-04 03:15:35 +08:00
help
Enable support for event file descriptors, eventfd. An eventfd can
be used as an event wait/notify mechanism together with POSIX calls
like read, write and poll.
posix: relocate Kconfig.eventfd to Kconfig.compat While event file descriptors (eventfd) are extremely useful, the API has still not been formalized as part of the POSIX specification. Therefore, move this to a separate Kconfig menu for "compat" (compatibility) features. Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
2024-05-24 00:19:58 +08:00
endmenu