Search Criteria
Package Details: artifact 2.1.5-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/artifact.git (read-only, click to copy) |
---|---|
Package Base: | artifact |
Description: | The design doc tool made for developers |
Upstream URL: | http://vitiral.github.io/artifact/ |
Keywords: | art artifact-app |
Licenses: | CC0, LGPL3+ |
Submitter: | rubdos |
Maintainer: | rubdos |
Last Packager: | rubdos |
Votes: | 2 |
Popularity: | 0.000000 |
First Submitted: | 2017-02-26 16:29 (UTC) |
Last Updated: | 2019-02-07 11:44 (UTC) |
Dependencies (6)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust, rustup) (make)
- cargo-webAUR (cargo-web-gitAUR) (make)
- mdbook (mdbook-gitAUR) (make)
- rust (rust-nightlyAUR, rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rustup) (make)
Latest Comments
zilbuz commented on 2019-02-07 11:17 (UTC) (edited on 2019-02-07 11:18 (UTC) by zilbuz)
Hi!
The last version of artifact (2.1.5-1) doesn't compile with the current build instructions. The structure of the sources changed a bit and the compilation is now done in two steps:
First compile the frontend: cargo-web deploy -p artifact-frontend --release --target=wasm32-unknown-unknown
Then build the application: cargo build -p artifact-app --release
The reason for this is that the compilation of the frontend has been removed from the build.rs script, but artifact-app still needs it to include the frontend.tar produced by the first step in the binary.
Moreover, is it still necessary to use cargo update? I think the dependencies have been updated upstream.