An open source python version of the Lindenmayer Systems.
Proof of concept project aiming at using concurrency to render fractal images with Qt and Qml
An open-source graphic toolkit for the creation, simulation and analysis of 3D virtual plants.
Same here. Have you found a relevant and reproducible way to get corrosion add the SDK root to the include directories ?
This bug is especially problematic in the context of cross platform builds, using e.g. iOS toolchains.
comment created time in 13 days
On educational purposes and discussion. Is there a discord server or whatever the tool to elaborate on qmetaobject-rs whenever issues don’t fit ? That would be awesome.
comment created time in 2 months
If I may, the same fix would be awesome for Qt >= 6.0.0, and that holds so far with 6.2.0 alpha ;-)
On 3 Jul 2021, at 19:44, ratijas ***@***.***> wrote:
Qt does not ship pre-built WebEngine component for Windows MinGW target, so we should find a way to exclude it from the list of default targets on that platform's target triple.
Running simple cargo build in qmetaobject-rs repository on Windows with MinGW environment results in build failure:
Compiling qmetaobject v0.2.2 (C:\Users\ratijas\projects\qmetaobject-rs\qmetaobject)
Compiling graph v0.1.0 (C:\Users\ratijas\projects\qmetaobject-rs\examples\graph)
The following warnings were emitted during compilation:
warning: src\webengine.rs:4:10: fatal error: QtWebEngine/QtWebEngine: No such file or directory
warning: #include <QtWebEngine/QtWebEngine>
warning: compilation terminated.
error: failed to run custom build command for
qmetaobject v0.2.2 (C:\Users\ratijas\projects\qmetaobject-rs\qmetaobject)
process didn't exit successfully:
C:\Users\ratijas\projects\qmetaobject-rs\target\debug\build\qmetaobject-4c86368b25d7a0a5\build-script-build(exit code: 1)
TARGET = Some("i686-pc-windows-gnu")
OPT_LEVEL = Some("0")
HOST = Some("x86_64-pc-windows-gnu")
running: "g++.exe" "-O0" "-ffunction-sections" "-fdata-sections" "-g" "-fno-omit-frame-pointer" "-m32" "-I" "C:\Users\ratijas\projects\qmetaobject-rs\qmetaobject" "-I" "C:/Qt/5.15.2/mingw81_32/include" "-Wall" "-Wextra" "-std=c++11" "-o" "C:\Users\ratijas\projects\qmetaobject-rs\target\i686-pc-windows-gnu\debug\build\qmetaobject-54d9dbd8cb0dbb47\out\rust_cpp\cpp_closures.o" "-c" "C:\Users\ratijas\projects\qmetaobject-rs\target\i686-pc-windows-gnu\debug\build\qmetaobject-54d9dbd8cb0dbb47\out\rust_cpp\cpp_closures.cpp"
cargo:warning=src\webengine.rs:4:10: fatal error: QtWebEngine/QtWebEngine: No such file or directory
cargo:warning= #include <QtWebEngine/QtWebEngine>
exit code: 1
Manually specify packages to exclude from workspace builds:
cargo build --workspace --exclude webengine Solution
I don't think politely asking Qt to ship pre-built WebEngine for MinGW is a viable solution, so let's try to mitigate the issue with Rust tools.
Cargo supports workspace-level package selection via default-members key. Cons:
Disables package for all platforms and targets; Requires typing in every package twice, except excluded ones. You might think that there's an exclude key for this task, but turns out it's for something else — preventing directories entirely from even being scanned by cargo. Anyway, I tried with Cargo.toml and .cargo/config.toml, and none of that works with triple-specific sections.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.
comment created time in 2 months
started time in 2 months
Hi, I'm considering switching many Qt-based projects to rust so I've been following this repo for a little while.
My last attempt at building both
qmetaobject-rs and any rust project using it as a crate for
0.2.2 ends up in inconsistent
rpath in the resulting binaries.
It can easily be fixed with
install_name_tool but I'm investigating
build.rs for a real fix.
Qt6.2.0-alpha (x86_64 + aarch64) from the online installer on a Mac M1.
I'm very new to rust but with some guidance I'll be glad to test and provide feedback.
comment created time in 3 months