File tree Expand file tree Collapse file tree 4 files changed +21
-2
lines changed Expand file tree Collapse file tree 4 files changed +21
-2
lines changed Original file line number Diff line number Diff line change @@ -7,6 +7,7 @@ build = "build.rs"
7
7
description = " Expose rust object to Qt and QML."
8
8
readme = " ../README.md"
9
9
license = " MIT"
10
+ categories = [" api-bindings" , " gui" ]
10
11
keywords = [" Qt" , " QML" , " QMetaObject" ,]
11
12
repository = " https://github.com/woboq/qmetaobject-rs"
12
13
Original file line number Diff line number Diff line change @@ -7,6 +7,7 @@ build = "build.rs"
7
7
description = " Manually maintained buildings for Qt value types"
8
8
readme = " README.md"
9
9
license = " MIT"
10
+ categories = [" api-bindings" , " ffi" ]
10
11
keywords = [" Qt" , " QtCore" , " QtGui" ]
11
12
repository = " https://github.com/woboq/qmetaobject-rs"
12
13
links = " qt"
Original file line number Diff line number Diff line change
1
+ # qttypes
2
+
3
+ This crate contains manually generated bindings to Qt basic value types.
4
+ It is meant to be used by other crates, such as the ` qmetaobject ` crate which re-expose them
5
+
6
+ The Qt types are basically exposed using the ` cpp ` crate. They have manually writen rust idiomatic
7
+ API which expose the C++ API.
8
+ These types are the direct equivalent of the Qt types and are exposed on the stack.
9
+
10
+ In addition, the build script of this crate expose some metadata to downstream crate that also
11
+ want to use Qt's C++ API:
12
+ - ` DEP_QT_VERSION ` : The Qt version as given by qmake
13
+ - ` DEP_QT_INCLUDE_PATH ` : The include directory to give to the ` cpp_build ` crate to locate the Qt headers
14
+ - ` DEP_QT_LIBRARY_PATH ` : The path containing the Qt libraries.
15
+
16
+ See the [ crate documentation] ( https://docs.rs/qttypes ) for more info.
Original file line number Diff line number Diff line change @@ -22,9 +22,10 @@ CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
22
22
//! API which expose the C++ API.
23
23
//! These types are the direct equivalent of the Qt types and are exposed on the stack.
24
24
//!
25
- //! In addition, the build script of this crate expose some metadata that are usefull to build.
25
+ //! In addition, the build script of this crate expose some metadata to downstream crate that also
26
+ //! want to use Qt's C++ API.
26
27
//! Build scripts of crates that depends directly from this crate will have the following
27
- //! environment variable when the build script is run:
28
+ //! environment variables set when the build script is run:
28
29
//! - `DEP_QT_VERSION`: The Qt version as given by qmake
29
30
//! - `DEP_QT_INCLUDE_PATH`: The include directory to give to the `cpp_build` crate to locate the Qt headers
30
31
//! - `DEP_QT_LIBRARY_PATH`: The path containing the Qt libraries.
You can’t perform that action at this time.
0 commit comments