Skip to content

Commit 946d2fa

Browse files
committed
Prepare v0.1.2 release
1 parent 2808424 commit 946d2fa

File tree

3 files changed

+29
-22
lines changed

3 files changed

+29
-22
lines changed

Cargo.lock

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ name = "up-rust"
3131
readme = "README.md"
3232
repository = "https://github.com/eclipse-uprotocol/up-rust"
3333
rust-version = "1.74.1"
34-
version = "0.1.1"
34+
version = "0.1.2"
3535

3636
[features]
3737
default = ["communication"]

README.md

Lines changed: 27 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -7,14 +7,39 @@ The crate can be used to
77
* implement uEntities that communicate with each other using the uProtocol [Communication Layer API](https://github.com/eclipse-uprotocol/up-spec/blob/v1.6.0-alpha.2/up-l2/api.adoc) over one of the supported transport protocols.
88
* implement support for an additional transport protocol by means of implementing the [Transport Layer API](https://github.com/eclipse-uprotocol/up-spec/blob/v1.6.0-alpha.2/up-l1/README.adoc).
99

10-
## Building
10+
## Using the Crate
11+
<!--
12+
`uman~up-language-using~1`
13+
Covers:
14+
- req~up-language-documentation~
15+
-->
16+
The crate needs to be added to the `[dependencies]` section of the `Cargo.toml` file:
17+
18+
```toml
19+
[dependencies]
20+
up-rust = { version = "0.1" }
21+
```
22+
23+
Most developers will want to use the Communication Level API and its default implementation
24+
which are provided by the `communication` module.
25+
26+
## Building from Source
1127
<!--
1228
`uman~up-language-building~1`
1329
Covers:
1430
- req~up-language-documentation~1
1531
-->
1632

17-
The crate can be built using the [Cargo package manager](https://doc.rust-lang.org/cargo/) from the root folder:
33+
First, the repository needs to be cloned using:
34+
35+
```sh
36+
git clone --recurse-submodules [email protected]:eclipse-uprotocol/up-rust
37+
```
38+
39+
The `--recurse-submodules` parameter is important to make sure that the git submodule referring to the uProtocol type definitions is being initialized in the workspace. The proto3 files contained in that submodule define uProtocol's basic types and are being compiled into Rust code as part of the build process.
40+
If the repository has already been cloned without the parameter, the submodule can be initialized manually using `git submodule update --init --recursive`.
41+
42+
The crate can then be built using the [Cargo package manager](https://doc.rust-lang.org/cargo/) from the root folder:
1843
<!--
1944
`impl~use-cargo-build-system~1`
2045
Covers:
@@ -26,8 +51,6 @@ Covers:
2651
cargo build
2752
```
2853

29-
The build requires an active connection to the internet because it needs to download and compile [uProtocol protobuf files](https://github.com/eclipse-uprotocol/up-spec/tree/v1.6.0-alpha.2/up-core-api) which define many of the core types used throughout the library.
30-
3154
The crate has some (optional) _features_ as documented in [lib.rs](src/lib.rs).
3255

3356
VSCode can be instructed to build all features automatically by means of putting the following into `./vscode/settings.json`:
@@ -46,22 +69,6 @@ The API documentation can be generated using
4669
cargo doc --no-deps --all-features --open
4770
```
4871

49-
## Using the Crate
50-
<!--
51-
`uman~up-language-using~1`
52-
Covers:
53-
- req~up-language-documentation~
54-
-->
55-
The crate needs to be added to the `[dependencies]` section of the `Cargo.toml` file:
56-
57-
```toml
58-
[dependencies]
59-
up-rust = { version = "0.1" }
60-
```
61-
62-
Most developers will want to use the Communication Level API and its default implementation
63-
which are provided by `communication` module.
64-
6572
## License
6673

6774
The crate is published under the terms of the [Apache License 2.0](LICENSE).

0 commit comments

Comments
 (0)