Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip shadow examples on MacOS due to inotify not being supported #218

Closed
wants to merge 1 commit into from

Conversation

timmattison
Copy link
Contributor

Motivation

  • MacOS does not support inotify but the shadow example code uses it. On MacOS these examples need to be removed in order for the compilation to be successful.

Modifications

Change summary

Added a check in CMakeLists.txt to detect if the system is an Apple operating system. If so, disable the shadow examples.

Testing

No CI for this but I needed to make this change in order to build the project on Mac OS.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

MacOS does not have inotify which the shadow examples depend on. The equivalent implementation requires kqueue and kevent from sys/event.h.

If the OS is MacOS then EXCLUDE_SHADOW, EXCLUDE_CONFIG_SHADOW, and EXCLUDE_SAMPLE_SHADOW are set.
@timmattison timmattison changed the title Skipping shadow code automatically on MacOS Skip shadow examples on MacOS due to inotify not being supported Feb 7, 2022
@HarshGandhi-AWS
Copy link
Contributor

At this moment, Device Client does not provide support for MacOS. This is mainly because of the shadow feature of device client which does not work on MacOS because of dependency issue which is expected and known. Even if your change over here disables Shadow feature on MacOS, we cannot push this change since it will give the wrong impression of device client is being supported on MacOS which is not true. For this reason we will have to close this review.

When we add support for Device Client on MacOS, we can reopen this review and merge your changes.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants