Search Criteria
Package Details: bazecor-git 1.3.10_rc.2.3305-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/bazecor-git.git (read-only, click to copy) |
---|---|
Package Base: | bazecor-git |
Description: | Graphical configurator for Dygma Raise. Development branch |
Upstream URL: | https://github.com/Dygmalab/Bazecor |
Licenses: | GPL3 |
Conflicts: | bazecor |
Provides: | bazecor |
Submitter: | TimQuelch |
Maintainer: | TimQuelch |
Last Packager: | TimQuelch |
Votes: | 5 |
Popularity: | 1.00 |
First Submitted: | 2022-03-23 02:20 (UTC) |
Last Updated: | 2024-01-12 00:07 (UTC) |
Dependencies (5)
- fuse (fuse2)
- git (git-gitAUR) (make)
- nvmAUR (nvm-gitAUR) (make)
- squashfs-tools (squashfs-tools-gitAUR) (make)
- yarn (corepackerAUR, yarn-pnpm-corepackAUR, yarn-berryAUR) (make)
Latest Comments
sammyF commented on 2024-04-17 10:53 (UTC)
any way to get bazecor to build, run and recognize the keyboard?
sagar794 commented on 2024-01-21 05:49 (UTC)
@TimQuelch I created a PR to resolve the
mksquashfs
error. Please feel free to leave any comments or feedback on the PR.TimQuelch commented on 2024-01-12 00:10 (UTC)
I've fixed the build commands and versioning issues, however I'm still running into the mksquashfs issue mentioned by rethus.
I'm open to any suggestions or PRs at https://github.com/TimQuelch/bazecor-git-aur
4s3ti commented on 2024-01-11 16:56 (UTC)
why is this out of date for so long? is the package maintainer out?
rethus commented on 2023-07-24 10:27 (UTC) (edited on 2023-07-24 10:36 (UTC) by rethus)
build faild with:
A short look into the git-repository shows, that they changed the command from
build:linux
tomake-lin
https://github.com/Dygmalab/Bazecor/blob/development/package.json#L21C6-L21C14
But even if I change this in the PKGBUILD during installing the package, I got an additional error:
TimQuelch commented on 2022-11-07 23:03 (UTC)
I've updated the PKGBUILD with nvm to use node 16.
devgioele commented on 2022-10-24 17:20 (UTC) (edited on 2022-10-24 18:41 (UTC) by devgioele)
After some debugging, I understood that the Node.js version must be
16
. Version19
makes theprepare
phase fail and version18
makes thebuild
phase fail.A possible solution is to specify in the
PKGBUILD
file that the version of thenodejs
package must be=16
. I think it should be put inmakedepends
. This causes problems, because almost every other software requiringnodejs
asks for the latest version.The preferred solution is to add
nvm
, the Node version manager, inmakedepends
and use it to temporarily set the Node.js version to16
. Runningnvm install 16 && nvm use 16
in the prepare phase, before runningyarn
, should do the job.devgioele commented on 2022-10-23 16:35 (UTC) (edited on 2022-10-23 16:40 (UTC) by devgioele)
There is only a white screen when I open the application. Looking at the build logs, the command
prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
outputsNo prebuilt binaries found (target=18.
with error code127
.I am not sure the error is related, but there is a comment in issue 45 that mentions
yarn rebuild
to fix it.Does anyone know a solution or have the same white screen?
TimQuelch commented on 2022-06-23 02:23 (UTC)
I've added it. I had assumed it was part of base-devel
lethedata commented on 2022-06-22 19:51 (UTC)
==> ERROR: Cannot find the git package needed to handle git sources.
PKGBUILD needs git in the makedepends section
makedepends=("yarn" "git")