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

feat(windows) additions to the API #68

Closed
wants to merge 85 commits into from
Closed

feat(windows) additions to the API #68

wants to merge 85 commits into from

Conversation

lucasfernog
Copy link
Contributor

No description provided.

steveklabnik and others added 30 commits February 21, 2018 16:40
they are out of date!
The documentation missed the compiletime requirement `libdbus-1-dev`.

When using this crate without having `libdbus-1-dev` installed, `cargo build` fails with the following error message on a linux system:

```
error: failed to run custom build command for `dbus v0.4.1`
process didn't exit successfully: `[…]target/debug/build/dbus-17d90d6172f41386/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: "`\"pkg-config\" \"--libs\" \"--cflags\" \"dbus-1\"` did not exit successfully: exit code: 1\n--- stderr\nPackage dbus-1 was not found in the pkg-config search path.\nPerhaps you should add the directory containing `dbus-1.pc\'\nto the PKG_CONFIG_PATH environment variable\nNo package \'dbus-1\' found\n"', libcore/result.rs:945:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.

warning: build failed, waiting for other jobs to finish...
error: build failed
```

Additionally, the examples missed `external create notify_rust;`. `cargo build` fails with the following message in that case:

```
1 | use notify_rust::Notification;
  |     ^^^^^^^^^^^ Maybe a missing `extern crate notify_rust;`?
```
Complement requirements documentation and examples
luckily the server never was considered stable, this changes it's
semantics severely, everything else should be fine
not supported anyway, sorry, not sorry
you aren't using that are you?
@hoodie hoodie self-requested a review March 11, 2020 21:47
@hoodie hoodie self-assigned this Mar 11, 2020
@lucasfernog lucasfernog marked this pull request as ready for review April 25, 2020 17:49
@lucasfernog
Copy link
Contributor Author

@hoodie can you review this PR? I'd be happy to fix or implement anything that's missing.

@hoodie
Copy link
Owner

hoodie commented Apr 25, 2020

oh yes, I was kinda waiting for you to rebase it and forgot about it since.
Could you rebase on top of master please? it's kinda hard to review this way

@lucasfernog
Copy link
Contributor Author

I think I messed up the branch here so I'm starting a new PR.

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.

7 participants