Simon Walker

@art-den: if you run `cargo update` (which should pick up `fitsio-sys` 0.5.1) and re-build, is your build fixed?

This is in your code right? Windows uses.32-bit pointers even on 64-bit systems, or at least cfitsio does. Can you change the `as *mut u64` to `as *mut u32` and...

~~I agree a size_t is the largest integer type for the machine representing the address space, but the function takes a pointer to size_t which for some reason is 32-bit...

Right: I found out why this is happening. It's not the size of a pointer, it's the size of a `size_t`. The bindings for `cfitsio` (in `fitsio-sys`) define `size_t` as...

``` $ cargo run -p fitsio --example reading_from_memory Compiling fitsio-sys v0.5.1 (C:\Users\Simon Walker\Desktop\rUSt-fitsio\fitsio-sys) warning: No version specifier available for pkg-config on windows, so the version of cfitsio used when compiling...

In the short term I can get around the link error by calling `check_status` rather using the `cfitsio` error reporting function. See [my branch](https://github.com/simonrw/rust-fitsio/pull/205/commits/896d9f21c278e4a2aba416048f2c3ed9334bc395). ~Unfortunately the example _still_ does not...

Er... it's inconsistent. I can run the code multiple times and get different answers :facepalm: That's going to be _really_ hard to debug on windows (for me anyway)!

Another option for you could be to use the `bindgen` feature of `fitsio` - add this to your `Cargo.toml`: ```toml fitsio = { version = "*", features = ["bindgen"], default-features...

Right. I've made some updates to the crate. I've mostly updated the bindings, which makes more sense for `msys2`. I can run the tests for `fitsio` including the example above...

Hi @d3v-null, thanks for raising this issue. I think you're right - the string handling needs to be better in `rust-fitsio`. I think you're probably right that these need to...