Zachary Catlin

I found that building docs from https://crates.io/api/v1/crates/web-view/0.7.2/download works just fine... once I remove Cargo.lock from the directory. I'm thinking maybe excluding Cargo.lock from the posted crate might help—you generally don't...

I confirm the same thing holds for the 0.7.0 and 0.7.1 releases, which also had doc-build failures on docs.rs. I'm going to put in a PR.

Hmmm... ```plain $ wget -O web-view-0.7.3.tar.gz 'https://crates.io/api/v1/crates/web-view/0.7.3/download' $ tar tzf web-view-0.7.3.tar.gz | egrep Cargo web-view-0.7.3/Cargo.lock web-view-0.7.3/Cargo.toml web-view-0.7.3/Cargo.toml.orig ``` Still including `Cargo.lock`. My previous PR's changes serve as documentation, but apparently...

Let's see what Cargo actually does. Starting with a fresh checkout of the `master` branch: ```plain $ cargo build && cargo doc [...] Finished dev [unoptimized + debuginfo] target(s) in...

As confirmation of the above: ```plain $ git mv examples not-really-examples ; git commit -m 'Testing' $ cargo clean ; cargo build [...] $ ls Cargo.lock Cargo.lock $ cargo package...

Per a discussion with @ajragusa today, this issue can be closed.

I closed this issue by mistake.

A possible approach that I've been kicking around in my head: unify the `cfs-sys` and `n2o4` crates, and in the build script, use the information `bindgen` has gathered about the...

That is supported by the `cmake` crate by setting the `CMAKE_GENERATOR` environment variable [1] for the Cargo invocation. [1] https://docs.rs/cmake/0.1.54/cmake/struct.Config.html#method.generator

> In my git bisecting I find that the git tag [`cfitsio-4.4.0` in the upstream repo](https://github.com/HEASARC/cfitsio/tree/cfitsio-4.4.0) does not support out-of-tree builds, but [`cfitsio-4.4.0`](https://github.com/HEASARC/cfitsio/tree/cfitsio-4.5.0) does[1](#user-content-fn-1-359665e991e74f9e40e546704d46536a). I think if we switch to...