-
Notifications
You must be signed in to change notification settings - Fork 914
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
only use CLOCK_MONOTONIC if not on osx #1142
Conversation
@flixr since you have contributed this code part recently can you please comment on this patch. |
Hm.. this actually seems to be a "bug" in boost, it doesn't handle the case that @ffurrer what boost version are you using? |
Falling back to system clock when a steady clock is requested on OSX doesn't sounds like a good behavior. If there is no "simple" fix it might require a custom implementation for OSX to achieve feature parity. |
FWIW, I just did some research on this topic for ROS2: ros2/rcutils#43 (comment) . We could use one of the solutions I pointed out there. |
I will merge this to fix the regression introduced by the switch to the steady time. Please create a follow up PR to support steady time on OS X (#1143). |
Actually it would make sense to also |
I would like to see a PR to implement steady for OS X rather sooner than later. Therefore I don't think we need a patch for the hopefully very short time period in between. |
@flixr I'm using 1.64:
|
I'm not sure if this is the cleanest solution, but it resolves the following compilation error: