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
The kqueue binding currently doesn't build at all on i686 and variants, because it doesn't use the right types when doing the binding for those architectures. However, the kqueue crate seems abandoned. Given this is a pretty small API, it shouldn't be too complex to do it ourselves instead.
To test the backend, run cargo test -p notify-backend-kqueue in BSD.
If you don't have a BSD on hand, you can get one running by installing Vagrant, checking out the next branch of this repo, and running vagrant up. That will bring up a FreeBSD11 virtual machine that you can then vagrant ssh into for developing. Use vagrant rsync or vagrant rsync-auto to sync up files to the virtual machine. However, note that this will bring up an x86_64 machine. To test on i686 you'll have to set up another one.
You don't have to reimplement the binding. If you find a kqueue binding that does what we want and is maintained, you can use that!
The goal here is to make Notify have a working backend on BSD on both x64 and x86. A bonus goal would be to support kqueue on macOS, as well.
The text was updated successfully, but these errors were encountered:
passcod
changed the title
Use kqueue native APIs directly to have it build on i*86
Use kqueue native APIs directly to 1) have it build on i*86 2) support macOS
Jan 2, 2018
passcod
changed the title
Use kqueue native APIs directly to 1) have it build on i*86 2) support macOS
Use kqueue native APIs directly to have it build on i686 / support macOS
Jan 2, 2018
passcod
changed the title
Use kqueue native APIs directly to have it build on i686 / support macOS
Use kqueue native APIs directly to support i686 / macOS
Jan 2, 2018
The kqueue binding currently doesn't build at all on i686 and variants, because it doesn't use the right types when doing the binding for those architectures. However, the kqueue crate seems abandoned. Given this is a pretty small API, it shouldn't be too complex to do it ourselves instead.
See failed Travis builds on i686-unknown-freebsd, for example this one: https://travis-ci.org/passcod/notify/jobs/322424840
You can also see the build failure locally by running
ci/cross-tests.sh build i686-unknown-freebsd
.Want to help?
Here is the documentation for the wrapper we currently use: https://docs.worrbase.com/rust/kqueue/
That should also give you its source.
kqueue is documented in its manual page: https://www.freebsd.org/cgi/man.cgi?kqueue(2)
To test the backend, run
cargo test -p notify-backend-kqueue
in BSD.If you don't have a BSD on hand, you can get one running by installing Vagrant, checking out the
next
branch of this repo, and runningvagrant up
. That will bring up a FreeBSD11 virtual machine that you can thenvagrant ssh
into for developing. Usevagrant rsync
orvagrant rsync-auto
to sync up files to the virtual machine. However, note that this will bring up anx86_64
machine. To test on i686 you'll have to set up another one.You don't have to reimplement the binding. If you find a kqueue binding that does what we want and is maintained, you can use that!
The goal here is to make Notify have a working backend on BSD on both x64 and x86. A bonus goal would be to support kqueue on macOS, as well.
The text was updated successfully, but these errors were encountered: