Package Details: rust-qt-binding-generator-git r365.41713b4-1

Git Clone URL: https://aur.archlinux.org/rust-qt-binding-generator-git.git (read-only, click to copy)
Package Base: rust-qt-binding-generator-git
Description: Generate code to build Qt applications with Rust
Upstream URL: https://invent.kde.org/sdk/rust-qt-binding-generator
Licenses: GPL2
Conflicts: rust-qt-binding-generator
Provides: rust-qt-binding-generator
Submitter: ZakCodes
Maintainer: None
Last Packager: gustawho
Votes: 1
Popularity: 0.000000
First Submitted: 2018-03-04 17:40 (UTC)
Last Updated: 2020-08-07 03:40 (UTC)

Latest Comments

1 2 Next › Last »

ohmyarch commented on 2019-06-13 09:24 (UTC)

@TheNiceGuy Fixed.

gpol commented on 2019-03-20 02:23 (UTC)

The executable no longer builds using cmake. Hence, the build no longer generate a package with an actual executable. The binding generator is now written in Rust and must not be build using Rust's tools (simple cargo build).

ZakCodes commented on 2018-03-15 23:28 (UTC)

Well at least we now how a version that works for us. Thanks a lot!

illis commented on 2018-03-15 01:12 (UTC)

The patch I provided seems to work for us Arch linux users, but it causes issues for others - you should be able to get by using that for now, till a better solution is found (its being worked on). https://phabricator.kde.org/D11078 https://phabricator.kde.org/D11232

ZakCodes commented on 2018-03-15 00:07 (UTC)

Nevermind just saw the content of your link. Did that change solve the problem for you?

ZakCodes commented on 2018-03-15 00:05 (UTC)

I get a segfault too. I really don't get it. I tried using a nightly compiler to see if it would work but still the same crash. I hope it will be fixed soon.

illis commented on 2018-03-14 23:53 (UTC)

All good. BTW, does the demo run on your machine? Or do you get a segfault? Seems there are at least a couple of us on Arch that are experiencing issues - https://bugs.kde.org/show_bug.cgi?id=389419

ZakCodes commented on 2018-03-13 12:23 (UTC)

You were right, I simply added cargo as a dependency and it automatically added all the packages that provide cargo as a possible dependencies and you only need to have one of them installed. Sorry for not knowing that.

illis commented on 2018-03-13 01:26 (UTC)

Or could we just change to rust -> rustup provides rust/cargo. If you make the dependency rustup then it forces me to replace rust with rustup.

ZakCodes commented on 2018-03-11 12:39 (UTC)

Sorry but cargo isn't a package. It's a binary that gets installed by rustup. The version of cargo can only be changed using rustup default $TOOLCHAIN. I'll still be trying to add some lines in the preparation to make sure that a default toolchain was setup.