From: xavierfortier1 <xavierfortier1@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: JLink
Date: Sat, 01 Feb 2025 04:11:58 +0100 [thread overview]
Message-ID: <20250201031158.7519020244@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54093@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2660 bytes --]
New comment by xavierfortier1 on void-packages repository
https://github.com/void-linux/void-packages/issues/54093#issuecomment-2628732274
Comment:
@classabbyamp Hey! I realised earlier today that the app that I am using is precompiled, so I cannot use libjaylink and I have not access to the code to compile it on my side... But I've managed to create a template that works (I installed jlink and programmed a devkit)! I feel it could be improved, especially where all the `ln` are used and the absence of checksum. I based this template on the one in the aur, so I am not sure if everything is ok. I am asking for your feedback if you have time. Thanks!
[Template](https://github.com/xavierfortier1/void-packages/tree/jlink/srcpkgs/jlink)
```bash
# Template file for 'jlink'
pkgname=jlink
version=8.12d
revision=1
archs="x86_64 aarch64 armv[67]* i686 ~*-musl"
hostmakedepends="curl"
short_desc="Segger JLink software & documentation pack for Linux"
maintainer="Xavier Fortier <xavier.fortier@proton.me>"
license="custom:Proprietary"
homepage="https://www.segger.com/downloads/jlink/"
changelog="https://www.segger.com/downloads/jlink/ReleaseNotes_JLink.html"
repository=nonfree
restricted=yes
nopie=yes
nostrip=yes
case "$XBPS_TARGET_MACHINE" in
x86_64)
_arch="x86_64"
;;
i686)
_arch="i386"
;;
aarch64)
_arch="arm64"
;;
armv[67]*)
_arch="arm"
;;
*)
return;
;;
esac
_archive="JLink_Linux_V${version/./}_${_arch}.tgz"
distfiles="https://www.segger.com/downloads/jlink/${_archive}"
do_fetch() {
env curl -o "${XBPS_SRCDISTDIR}/${pkgname}-${version}/${_archive}" \
-d accept_license_agreement=accepted -d non_emb_ctr=confirmed \
"${distfiles}"
}
do_install() {
vmkdir opt/SEGGER/JLink
vmkdir usr/bin
vmkdir etc
vmkdir usr/lib/udev/rules.d
vmkdir usr/share/pixmaps
vmkdir "usr/share/licenses/${pkgname}"
vmkdir "usr/share/doc/${pkgname}"
vinstall "${FILESDIR}/JLink.svg" 644 usr/share/pixmaps
for f in J* DevProExe DDC* Samples ETC README.txt Firmwares GDBServer lib*; do
vcopy "${f}" opt/SEGGER/JLink
done
if [ "${XBPS_TARGET_MACHINE}" = "x86_64" ]; then
vcopy x86 opt/SEGGER/JLink
fi
vcopy ETC/JFlash etc
vsed -i 99-jlink.rules -e 's/0x//g'
vinstall 99-jlink.rules 644 usr/lib/udev/rules.d
vinstall "${FILESDIR}/99-jlink-cmsis-dap.rules" 644 usr/lib/udev/rules.d
for f in J* DevProExe; do
ln -s "/opt/SEGGER/JLink/${f}" "${DESTDIR}/usr/bin"
done
ln -s /opt/SEGGER/JLink/Doc/LicenseIncGUI.txt "${DESTDIR}/usr/share/licenses/${pkgname}"
for f in Doc/Manuals/* Doc/ReleaseNotes; do
ln -s "/opt/SEGGER/JLink/${f}" "${DESTDIR}/usr/share/doc/${pkgname}"
done
}
```
next prev parent reply other threads:[~2025-02-01 3:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 0:13 [ISSUE] " xavierfortier1
2025-01-24 3:00 ` classabbyamp
2025-01-24 3:15 ` [ISSUE] [CLOSED] " xavierfortier1
2025-01-24 3:15 ` xavierfortier1
2025-02-01 3:10 ` xavierfortier1
2025-02-01 3:11 ` xavierfortier1 [this message]
2025-02-01 4:21 ` classabbyamp
2025-02-01 14:32 ` xavierfortier1
2025-02-01 14:41 ` classabbyamp
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=20250201031158.7519020244@inbox.vuxu.org \
--to=xavierfortier1@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).