eif_build: Move from examples directory into its own workspace

Now that we've extended the eif_build tool to be very useful outside of
example use cases, let's make it its own stand alone target. You can
easily compile it with

  $ cargo build -p eif_build

Signed-off-by: Alexander Graf <[email protected]>

Cargo.toml

@@ -24,3 +24,9 @@ aws-nitro-enclaves-cose = "0.5"
 openssl = "0.10"
 serde_cbor = "0.11"
 chrono = { version = "0.4", default-features = false, features = ["clock"]}
+
+[workspace]
+members = [
+    ".",  # aws-nitro-enclaves-image-format
+    "eif_build",  # The eif_build CLI tool
+]

README.md

@@ -25,10 +25,10 @@ This project is licensed under the Apache-2.0 License.
 To compile the `eif_build` tool, run
 
 ```sh
-$ cargo build --examples --release
+$ cargo build --all --release
 ```
 
-The resulting binary will be under `./target/release/examples/eif_build`.
+The resulting binary will be under `./target/release/eif_build`.
 
 ## Usage
 

eif_build/Cargo.toml

@@ -0,0 +1,20 @@
+[package]
+name = "eif_build"
+version = "0.2.0"
+authors = ["The AWS Nitro Enclaves Team <[email protected]>"]
+edition = "2018"
+license = "Apache-2.0"
+description = "This CLI tool provides a low level path to assemble an enclave image format (EIF) file used in AWS Nitro Enclaves."
+repository = "https://github.com/aws/aws-nitro-enclaves-image-format"
+readme = "README.md"
+keywords = ["Nitro", "Enclaves", "AWS", "EIF"]
+rust-version = "1.68"
+
+[dependencies]
+aws-nitro-enclaves-image-format = { path = ".." }
+sha2 = "0.9.5"
+serde = { version = ">=1.0", features = ["derive"] }
+serde_json = "1.0"
+clap = "3.2"
+chrono = { version = "0.4", default-features = false, features = ["clock"]}
+