Will
Will
How do these options look? (Example snippet w/ no sanitizers, no tests) ``` $ cmake -S . -B out/tmp -DBUILD_TEST=OFF -DBUILD_SAN=OFF ... -- wtr.hdr_watcher: Added (BUILD_HDR=ON) -- watcher-c-hdr: Added (BUILD_HDR=ON)...
Where the full set of options is: ``` option(BUILD_LIB "Create a target for the watcher-c libraries" ON) option(BUILD_BIN "Create a target for the CLI binaries" ON) option(BUILD_HDR "Create a target...
Fixed in https://github.com/e-dant/watcher/commit/55e6b15781f4933ed1278b81cecdcc3194d3a3b0, I'll cut a release if https://github.com/e-dant/watcher/issues/59 is resolvable
Well... Let me fixup some build errors first...
> Another related thing: is it desirable/needable to install the `wtr.watcher` and `tw` binary in the system path? At least, maybe the `tw` binary should be renamed for something more...
For the naming, I've been hesitant to change things in case there are people relying on them as-is. (But I think we can/should do it.) However, if we change the...
I am unfortunately not a CMake expert, and I'm not sure the best way to help. However, I'm more than happy to change things in ways that make our CMake...
> For the record, I opened a PR to add watcher to Homebrew: https://github.com/Homebrew/homebrew-core/pull/201096 This is so awesome!
thinking and looking. might not be able to get around to this one today.
One thing we could do is try to create new inotify instances *per-filesystem*. (As a workaround, this would be somewhat equivalent to launching new instances of watcher on a per-filesystem...