problem with glutin on osx

[rsaarelm]

problem with glutin on osx

[rsaarelm]

I don't have a Mac so I can't test this directly, but it looks like the function on that line has been given an implementation in the current Glutin master, while it's still marked as unimplemented and causing the runtime crash the crates.io version Magog is using.

If you know how to mess with Cargo files, you could change glutin to be fetched from the github master instead of the crates.io version (actually I think you'll need to get a local copy of calx, change its Cargo.toml since that's where glium is being referenced, then point your local magog's Cargo.toml to your local calx, then try again).

If you haven't been already troubleshooting Cargo configs by hand and that sounds too confusing, you can just wait for the updated Glium to end up on crates.io and then either take your chances doing a "cargo update" on magog yourself or wait for me to release the next "Updated dependencies/to latest Rust" commit.

[jlmitch5]

Funny you should mention the dependency thing...I'm a bit embarrassed to say I spent several hours playing around with Cargo dependencies yesterday trying to get things updated so Magog would compile on yesterday's nightly...until I saw your note on Phage that I should use the version you compiled with.

Also a question about dependency stuff if you don't mind me asking: is there an easy way to tell where the crates.io container is actually at in terms of the repo? I've noticed that people will commit "bump to x version", even when they haven't pushed that to Cargo. This makes it pretty hard to try to fix things.

[rsaarelm]

After a quick look-around, I didn't see anything associating the crates containers with git hashes. Makes sense, someone might want to push things to crates without having any kind of public git repository for it, so crates might have just the file set snapshots and semver numbers.

[jlmitch5]

yeah...you get like thread '

' panicked at 'not yet implemented', /Users/jmitchell/.cargo/registry/src/github.com-1ecc6299db9ec823/glutin-0.0.12/src/cocoa/mod.rs:591

but that doesn't seem to be related to a commit hash.

[jlmitch5]

So to hand update nested dependencies, you need to fork each library and specify the dependency in its Cargo.toml, correct?

[rsaarelm]

If you want to try a quick and dirty approach, you can just go in your ~/.cargo folder and put a different fileset in the directory where it builds the package from. If the libraries have some simple oneliner fixes they need to build with the latest Rust, I generally just edit the sources in the ~/.cargo cache directly to do trivial changes. Haven't tried changing the whole fileset, but it might work as well if the versions are close to each other.

[rsaarelm]

OSX should be working now.