Search Criteria
Package Details: armorpaint-git 0.9.r2900.gef390132-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/armorpaint-git.git (read-only, click to copy) |
---|---|
Package Base: | armorpaint-git |
Description: | ArmorPaint is a software for 3D PBR texture painting |
Upstream URL: | https://armorpaint.org/ |
Keywords: | 3D gamedev graphics painting PBR |
Licenses: | zlib |
Conflicts: | armorpaint |
Provides: | armorpaint |
Submitter: | juliotux |
Maintainer: | None |
Last Packager: | juliotux |
Votes: | 10 |
Popularity: | 0.000040 |
First Submitted: | 2020-03-22 18:08 (UTC) |
Last Updated: | 2022-03-26 14:13 (UTC) |
Dependencies (12)
- alsa-lib
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- libxinerama (libxinerama-randr-gitAUR)
- mesa (mesa-minimal-gitAUR, mesa-gitAUR, mesa-wsl2-gitAUR, amdonly-gaming-mesa-gitAUR, mesa-amd-bc250AUR, mesa-amber)
- nodejs (nodejs-lts-fermiumAUR, nodejs-gitAUR, python-nodejs-wheelAUR, nodejs-lts-hydrogen, nodejs-lts-iron)
- clang (llvm-rocm-gitAUR, llvm-gitAUR, clang-minimal-gitAUR, clang17-binAUR) (make)
- gcc (gcc-gitAUR, gccrs-gitAUR, gcc11AUR, gcc-snapshotAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR) (make)
- make (make-gitAUR) (make)
- nodejs (nodejs-lts-fermiumAUR, nodejs-gitAUR, python-nodejs-wheelAUR, nodejs-lts-hydrogen, nodejs-lts-iron) (make)
- vulkan-headers (vulkan-headers-gitAUR) (make)
Latest Comments
1 2 Next › Last »
hellishbliss commented on 2024-12-17 22:40 (UTC) (edited on 2024-12-18 01:34 (UTC) by hellishbliss)
Regarding the comment by Graith95, the same can be used for armorlab, obviously change the checksums/git repo/edit desktop and sh files.
Also the pkgbuild fails as it looks for "LICENSE.md" when it needs to be "license.md" on line 50.
Graith95 commented on 2024-09-10 01:56 (UTC)
I have a working PKGBUILD for the 1.0 alpha at https://gist.github.com/GraithTiger/ebab9f777e62b52fe23141622c5669a3
The-Anathema commented on 2024-06-22 22:03 (UTC)
I intend to fix this one as well since I created and took on maintenance of stable (non-git, v0.9 at time of writing).
Right now that's not going to happen though, upstream is completely broken, some of these errors would be trivial to fix but I don't have the time to deep dive the codebase to fix it.
fatal error: too many errors emitted, stopping now [-ferror-limit=] 20 errors generated. make: *** [makefile:12: krom.o] Error 1
It appears the entire project is currently undergoing some kind of restructuring, Kinc/make has been turned to just make, files have moved, etc. I suspect most of these issues will be ironed out in a few weeks when they finish restructuring.
sem.z commented on 2024-03-06 13:32 (UTC) (edited on 2024-03-06 13:47 (UTC) by sem.z)
Fixed
pkgver
build error:But unfortunately still unable to build. Some people right now also have troubles, see - https://github.com/armory3d/armortools/issues/1671.
juliotux commented on 2023-09-14 15:42 (UTC)
Hi @AmonDeShir, I orphaned the package. Feel free to adopt it.
AmonDeShir commented on 2023-09-14 00:40 (UTC) (edited on 2023-09-14 00:43 (UTC) by AmonDeShir)
I fixed build errors:
I changed GitHub URL because main repo was renamed to armortools. I also removed nodejs from dependencies (armorpaint has build-in v8). Furthermore, I had troubles with compilation using clang: "incompatible pointer to integer conversion passing 'zui_node_socket_t ' (aka 'struct zui_node_socket ') to parameter of type 'int' [-Wint-conversion]", in clang14 it was only a warning, but since clang15 it is an error now, unfortunately arch uses clang16. I failed to get kmake to use clang14 instead of the default clang16, so as a workaround, I changed clang to GCC.
mbway commented on 2023-02-11 17:56 (UTC) (edited on 2023-02-11 17:57 (UTC) by mbway)
The package fails to build.
Sources/Main.hx
has moved toarmorpaint/Sources/Main.hx
build/krom
has moved toarmorpaint/build/krom
lehthanis commented on 2021-11-03 18:14 (UTC)
I'm using an Nvidia RTX 2080 and I get incredible gpu usage spike and overheat and a framerate of about 1 frame every 1-3 seconds....it's bad...what am I doing wrong? Should I submit this to the devs?
juliotux commented on 2021-08-28 14:23 (UTC)
@Blaster84x package fixed.
1 2 Next › Last »