Package Details: prjapicula-git 0.32.r5.gf4a0b4a-1

Git Clone URL: https://aur.archlinux.org/prjapicula-git.git (read-only, click to copy)
Package Base: prjapicula-git
Description: Project Apicula bitstream documentation for Gowin FPGAs
Upstream URL: https://github.com/YosysHQ/apicula
Licenses: MIT
Conflicts: prjapicula
Provides: prjapicula
Submitter: thotypous
Maintainer: thotypous (pepijndevos)
Last Packager: thotypous
Votes: 1
Popularity: 0.53
First Submitted: 2025-02-04 12:39 (UTC)
Last Updated: 2026-05-18 22:14 (UTC)

Latest Comments

thotypous commented on 2026-05-17 12:50 (UTC)

@inverseinductor Those files are present in the current pepijndevos/apicula:1.9.10.03 image; building locally in my machine also shows chipdb generation completing for those devices. This looks more like a stale/partial makepkg srcdir or Apptainer cache. Please try a clean build with makepkg -Ccsf or remove src/, pkg/, *.sif, *.squashfs, and optionally run apptainer cache clean.

inverseinductor commented on 2026-05-17 04:37 (UTC)

for version 0.32.r5.gf4a0b4a-1 The chipdb_builder.py is missing the following files: GW1NR-9C.fse GW2A-18.fse GW1N-4.fse GW1NSR-4C.fse GW1N-9.fse GW5AST-138C.fse GW1N-1.fse GW2A-18C.fse GW1NZ-1.fse GW5A-25A.fse Looks like it might be an issue with the docker image?

pepijndevos commented on 2026-03-28 16:57 (UTC)

I am not very familiar with arch package maintenance but maybe it'll come in handy one day. Now that all three apicula packages are up to date maybe it's fine for this one to use gowin IDE for those who want the true from source git experience as opposed to a pypi release or prebuilt database files.

thotypous commented on 2026-03-24 21:01 (UTC)

@pepijndevos thank you for the heads up about the new depends.

I added you as co-maintainer, please feel free to modify the PKGBUILD as you see fit, it is an honor to have an upstream developer here.

Please just consider my previous comment about release tagging in GitHub. It's important for me to ensure consistency between the pkgver and the actually packaged binaries because I make this PKGBUILD in an automated pipeline.

pepijndevos commented on 2026-03-23 06:34 (UTC)

I don't think downloading Godwin ide is a very useful thing to do for end users. Nothing wrong with having this option but most people are probably better off using the other git package that uses our data.tgz database files.

I'll also point out that our python deps are only numpy, fastcrc and msgspec, the rest are or were development packages.

If anything this should be seen as a developer package.

thotypous commented on 2025-07-17 02:25 (UTC)

@Marichan I emailed pepijndevos for suggestions before creating this package and he made the same suggestion of getting the fuzzer results generated by their CI from GitHub Releases.

The main problem I see with that approach is that we would not guarantee the pkgver of this package would match the version of the shipped files. Suppose they just pushed something to the git repo, and unluckily you run makepkg before GitHub CI finishes to run. You would generate a package with updated pkgver, but older chipdb files. Then, you would think you are using the latest chipdb, but you would be using a stale version.

I see no way to fix this unless they tag their downloads with the git commit hash, instead of shipping everything as 0.0.0.dev.

Even if this is fixed, I'm not sure if we would be following the correct package naming convention if we used prebuilt chipdb. Prebuilt packages theoretically should be suffixed with -bin, but I've never seen something -git-bin. I have seen -nightly-bin stuff, but this package does not use a nightly snapshot. It would be nice to research if there is some similar situation in AUR and borrow their naming conventions (but IMHO this is a less important issue).

Marichan commented on 2025-07-16 14:33 (UTC)

@thotypous thanks! One of the maintainer meanwhile also suggested that we could pull all the built pickles chipDB from their github. I am not sure if it is better than building them locally, but it would drop the apptainer dependency. I will let you decide the best course anyway

thotypous commented on 2025-07-15 22:48 (UTC)

@Marichan I didn't notice they added that GWVERSION file. Thanks a lot for the patch, I just applied it!

Marichan commented on 2025-07-15 22:36 (UTC) (edited on 2025-07-15 22:44 (UTC) by Marichan)

Hi, the fuzzer version has been bumped from 1.9.8 to 1.9.10.03. While just bumping the version would be fine I think that this being a git package and all it should use the GWVERSION file rpesent in the repo to grab the correct version. This patch to the PKGBUILD should do it:

--- PKGBUILD-og 2025-07-16 00:32:34.738284092 +0200
+++ PKGBUILD    2025-07-16 00:24:41.147422126 +0200
@@ -3,14 +3,11 @@

 _pkgname="prjapicula"
 pkgname="$_pkgname-git"
-pkgver=0.15.r33.g15614ef
-_fuzzerver=1.9.8
+pkgver=0.21.r0.gfffb2a3
 pkgrel=1
 pkgdesc="Project Apicula bitstream documentation for Gowin FPGAs"
 url="https://github.com/YosysHQ/apicula"
 _pkgsrc="apicula"
-_fuzzer="fuzzer-$_fuzzerver"
-_fuzzerimg="docker.io/pepijndevos/apicula:$_fuzzerver"
 source=(
   "$_pkgsrc"::"git+$url.git"
 )
@@ -49,6 +46,9 @@
 }

 prepare() {
+  _fuzzerver=$(cat "$_pkgsrc/GWVERSION")
+  _fuzzer="fuzzer-$_fuzzerver"
+  _fuzzerimg="docker.io/pepijndevos/apicula:$_fuzzerver"
   apptainer pull -F $_fuzzer.sif docker://$_fuzzerimg
   apptainer sif dump 4 $_fuzzer.sif >$_fuzzer.squashfs
   mkdir -p $_fuzzer