Github messages for voidlinux
 help / color / mirror / Atom feed
From: jason1987d <jason1987d@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] [WIP] New package: KataGo-1.11.0
Date: Fri, 22 Jul 2022 15:40:29 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38190@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]

There is a new pull request by jason1987d against master on the void-packages repository

https://github.com/jason1987d/void-packages KataGo
https://github.com/void-linux/void-packages/pull/38190

[WIP] New package: KataGo-1.11.0
#### Testing the changes
- I tested the changes in this PR: NO
This is a work in progress.

#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): YES

<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->

Main question so far, CMakeLists.txt is found in ${wrksrc}/cpp, what configure_flag or other variable do I set to make it work and find that? I've set cmake_builddir to that which didn't work.

I discussed briefly with @Chocimier about this package when I submitted the new package q5go and will have other architecture questions.

This package has multiple backends: OpenCL, Eigen, TensorRT. I use an AMD Ryzen system and notice I already have mesa-opencl installed, I see there is another opencl implementation for Nvidia cards, and I suppose others (i.e. Intel) could even be ported to void. Eigen is available in the repos. Would this be multiple templates i.e. KataGo-OpenCL KataGo-Eigen etc or would I need to set up KataGo as some sort of metapackage?

A patch file from https://github.com/void-linux/void-packages/pull/38190.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-KataGo-38190.patch --]
[-- Type: text/x-diff, Size: 1298 bytes --]

From f504bdf8c370a2538431367966cd71b2f3df190a Mon Sep 17 00:00:00 2001
From: Jason Manley <jason@jasondavid.tv>
Date: Thu, 21 Jul 2022 23:01:22 -0500
Subject: [PATCH] New package: KataGo-1.11.0

---
 srcpkgs/KataGo-OpenCL/template | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 srcpkgs/KataGo-OpenCL/template

diff --git a/srcpkgs/KataGo-OpenCL/template b/srcpkgs/KataGo-OpenCL/template
new file mode 100644
index 000000000000..b86474678ad4
--- /dev/null
+++ b/srcpkgs/KataGo-OpenCL/template
@@ -0,0 +1,23 @@
+# Template file for 'KataGo-OpenCL'
+pkgname=KataGo-OpenCL
+version=1.11.0	
+revision=1
+#archs="i686 x86_64"
+wrksrc="KataGo-${version}"
+#create_wrksrc=yes
+build_style=cmake
+#configure_args=""
+make_build_args="-DUSE_BACKEND=OPENCL"
+#make_install_args=""
+#conf_files=""
+#make_dirs="/var/log/dir 0755 root root"
+hostmakedepends=""
+makedepends="mesa-opencl"
+depends=""
+short_desc="KataGo Go/Weiqi/Baduk analysis engine (OpenCL backend)"
+maintainer="Jason Manley <jason@jasondavid.tv>"
+license="GPL-3.0-or-later"
+homepage="https://github.com/lightvector/KataGo/"
+#changelog=""
+distfiles="https://github.com/lightvector/KataGo/archive/refs/tags/v${version}.tar.gz"
+checksum=3f63aa5dfaab861360fd6f9548aa7f552b007cac7e90c99089d3bb4bb4b9d451

             reply	other threads:[~2022-07-22 13:40 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 13:40 jason1987d [this message]
2022-07-22 15:47 ` [PR REVIEW] " Chocimier
2022-07-22 15:47 ` Chocimier
2022-07-22 15:47 ` Chocimier
2022-07-22 15:47 ` Chocimier
2022-07-22 17:26 ` [PR PATCH] [Updated] " jason1987d
2022-07-22 17:26 ` jason1987d
2022-07-22 18:19 ` jason1987d
2022-07-22 20:19 ` Chocimier
2022-07-22 21:24 ` jason1987d
2022-07-22 21:24 ` jason1987d
2022-07-22 21:52 ` jason1987d
2022-07-22 22:04 ` jason1987d
2022-07-22 22:09 ` [PR PATCH] [Updated] " jason1987d
2022-07-23 13:47 ` jason1987d
2022-07-23 13:48 ` jason1987d
2022-07-23 16:43 ` jason1987d
2022-07-23 16:49 ` jason1987d
2022-07-24  1:47 ` jason1987d
2022-07-25 16:34 ` [PR REVIEW] " Chocimier
2022-07-25 16:34 ` Chocimier
2022-07-26 13:33 ` [PR PATCH] [Updated] " jason1987d
2022-07-26 13:36 ` jason1987d
2022-07-26 15:19 ` [PR PATCH] [Updated] " jason1987d
2022-07-27 18:56 ` Chocimier
2022-07-29 21:16 ` [PR PATCH] [Updated] " jason1987d
2022-07-29 21:17 ` jason1987d
2022-07-29 21:18 ` jason1987d
2022-07-29 21:30 ` jason1987d
2022-07-30  1:29 ` jason1987d
2022-07-30  1:40 ` jason1987d
2022-07-30  1:40 ` jason1987d
2022-07-30  1:40 ` jason1987d
2022-07-30  1:41 ` jason1987d
2022-07-30  1:41 ` jason1987d
2022-07-30  1:45 ` jason1987d
2022-07-30  1:48 ` jason1987d
2022-07-30 13:46 ` Chocimier
2022-07-30 18:08 ` jason1987d
2022-07-30 18:19 ` [PR PATCH] [Updated] " jason1987d
2022-07-31 21:14 ` jason1987d
2022-08-02 17:57 ` [PR REVIEW] " Chocimier
2022-08-02 17:57 ` Chocimier
2022-08-02 21:15 ` jason1987d
2022-08-02 21:45 ` Chocimier
2022-08-03  4:32 ` [PR PATCH] [Updated] " jason1987d
2022-08-12 14:38 ` jason1987d
2022-09-11  5:22 ` jason1987d
2022-09-11  5:24 ` [PR PATCH] [Closed]: " jason1987d
2022-09-11  5:24 ` [PR PATCH] [Updated] " jason1987d
2022-09-11 13:53 ` jason1987d

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38190@inbox.vuxu.org \
    --to=jason1987d@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).