You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a use-case where I would like to manage timezone settings on the device depending on regional deployment. My intention was to use localtime() which is a common libc implementation to support timezone via the TZ environment variable. But this does not appear to be supported in Zephyr Project when I look in https://github.com/zephyrproject-rtos/zephyr/tree/main/lib/libc/common/source/time. It appears to only support UTC time.
This implementation seems to be shared between Picolibc (this is what I am using) and Newlib. As I understand both Picolibc and Newlib do support timezones but Zephyr Project has decided to override this (in favor of portability?)?
I am not sure what my options would be, besides doing a major rewrite of the common libc. Maybe I am missing something obvious? I can not imagine that this use-case is that exotic but I could not find much discussions on this topic in Discussions and Issues.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have a use-case where I would like to manage timezone settings on the device depending on regional deployment. My intention was to use
localtime()which is a common libc implementation to support timezone via the TZ environment variable. But this does not appear to be supported in Zephyr Project when I look in https://github.com/zephyrproject-rtos/zephyr/tree/main/lib/libc/common/source/time. It appears to only support UTC time.This implementation seems to be shared between Picolibc (this is what I am using) and Newlib. As I understand both Picolibc and Newlib do support timezones but Zephyr Project has decided to override this (in favor of portability?)?
I am not sure what my options would be, besides doing a major rewrite of the common libc. Maybe I am missing something obvious? I can not imagine that this use-case is that exotic but I could not find much discussions on this topic in Discussions and Issues.
Appreciate your feedback.
Best Regards
Mirza
Beta Was this translation helpful? Give feedback.
All reactions