- 05 Apr, 2018 1 commit
-
-
Sebastian Dröge authored
-
- 04 Apr, 2018 1 commit
-
-
Sebastian Dröge authored
-
- 01 Apr, 2018 2 commits
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- 21 Mar, 2018 1 commit
-
-
Fernando Jiménez Moreno authored
-
- 20 Mar, 2018 7 commits
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- 19 Mar, 2018 19 commits
-
-
François Laignel authored
There are different implementations and signatures for `get_pollfd` depending on whether the target platform is unix or windows. When generating the doc, we need both implementations to appear regardless of the target platform. This commit is inspired by the way Rust `std` library deals with `process::Command` OS dependent variants (https://doc.rust-lang.org/std/process/struct.Command.html#impl-CommandExt). Documentation can't be accurate though as we can't use the`std::os::windows` on `unix` and vice versa. As a workaround a fake fd class matching the other platform is declared. This could be further enhanced once `#[doc(cfg(...))]` is stabilized (https://github.com/rust-lang/rust/issues/43781) by declaring `#[doc(cfg(unix))]` or `#[doc(cfg(windows))]` instead of the hard coded comments `This is supported on **Windows/Unix** only`. Unfortunately, these comments disappear when generating will `--all-features` because they are not part of the documentation in the gir file.
-
François Laignel authored
Fixes https://github.com/sdroege/gstreamer-rs/pull/93
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
François Laignel authored
When feature `dox` is selected but not `futures`, the `futures` crate is not available as a dependency leading to a "can't find crate for `futures`" error.
-
- 16 Mar, 2018 3 commits
-
-
François Laignel authored
Fixes https://github.com/sdroege/gstreamer-rs/pull/92
-
Sebastian Dröge authored
-
Sebastian Dröge authored
This should improve logging performance if the threshold is not high enough.
-
- 14 Mar, 2018 1 commit
-
-
Sebastian Dröge authored
-
- 12 Mar, 2018 1 commit
-
-
Fernando Jiménez Moreno authored
-
- 07 Mar, 2018 1 commit
-
-
Sebastian Dröge authored
-
- 02 Mar, 2018 3 commits
-
-
Mathieu Duponchelle authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-