Reorganize project infrastructure

[ebkalderon]

Reorganize project infrastructure

[ebkalderon]

It seems that splitting the engine into separate sub-crates causes issues with unit testing (see the annotation in pull request #15). Currently, the unit tests are preserved as integration-style tests, but this is not idiomatic Rust practice. If anyone has better ideas on the reorganization process, please discuss them here.

[kvark]

We don't have this problem in GFX. Perhaps, you could follow the same structure?

We have most of the crates inside the same repository, and they are in sub-folders (src/core, src/render, src/backend/gl, etc). Each has its own tests. Then there is a "meta" crate, which is just an empty src/lib.rs, it depends on all the sub-crates via Cargo.toml. Thus, calling cargo build builds everything, calling cargo test tests everything. This meta crate doesn't need to be uploaded to crates.io, it's just for developer convenience.

Edit: pending confirmation that our local tests are indeed called...

[ebkalderon]

@kvark After playing around with my local copy of the repository, I can conclude that while cargo build does indeed build everything and cargo clean does clean everything, this behavior does not appear to extend to cargo test. Can you confirm?

[ebkalderon]

A general question: should the amethyst_engine crate exist? If not, should its functionality be put in the top-level amethyst crate?

[kvark]

Isn't Amethyst a game engine? What is supposed to be in amethyst_engine then?

[ebkalderon]

It is indeed! I was wondering whether the code in amethyst_engine should be moved to the top-level amethyst crate, or if it should stay in its own crate.

[ebkalderon]

Engine restructuring has been completed with commit 449dd3a, so I'm closing this issue.

As of now, amethyst/tools#4 remains open. The public 0.2.0 release will occur when that issue is resolved.