Arch Linux User Repository

I switched to the mold linker on purpose to reduce the enormous link times (with LTO) of this project and get better error messages when the linking fails due to the patched buildscript. If you don't like that, use qmake -unset <flags> to remove it.

@bionade I was debugging an issue I am having with my first VESC so I thought it could be a big on the version I was using. But when I installed this package I was compiling this everyday along with the other updates. My laptop is not so good sso that took a lot of time so I ended up using the appimage. I also gave up :)

@Gpereira: Would you like to step up to maintain this pkg? Seems like you care about having the latest version of it installed, which I really don't. I'm tired of constantly fixing the patches for this pkg.

@GPereira: No, this fix definetely works (and it would absolutely make 0 sense to not work from the current qmake script, either).

[name:~/dir/vesc_tool-git]└2 master* ± mv vesc_tool-git-1:r1412.7c02f7f-1-x86_64.pkg.tar.zst test.tar.zst
[name:~/dir/vesc_tool-git]└2 master* 2 ± tar tvf test.tar.zst
-rw-r--r-- root/root      8105 2024-04-16 10:31 .BUILDINFO
-rw-r--r-- root/root       440 2024-04-16 10:31 .MTREE
-rw-r--r-- root/root       574 2024-04-16 10:31 .PKGINFO
drwxr-xr-x root/root         0 2024-04-16 10:31 usr/
drwxr-xr-x root/root         0 2024-04-16 10:31 usr/bin/
-rwxr-xr-x root/root  19967256 2024-04-16 10:31 usr/bin/vesc_tool
drwxr-xr-x root/root         0 2024-04-16 10:31 usr/share/
drwxr-xr-x root/root         0 2024-04-16 10:31 usr/share/applications/
-rw-r--r-- root/root       196 2024-04-16 10:31 usr/share/applications/vesc-tool.desktop
drwxr-xr-x root/root         0 2024-04-16 10:31 usr/share/icons/
-rw-r--r-- root/root      5484 2024-04-16 10:31 usr/share/icons/vesc-tool.png

I guess you have a dirty build environment. Please build in a clean chroot or (clean & fresh) docker container, ideally with the extra-x86_64-build script from devtools.

The fix seems not effective. The executable is still called vesc_tool_6.05 even on a clean build

@GPereira: Fixed, thx for the heads-up!

The executable is:

/usr/bin/vesc_tool_6.05

and not:

/usr/bin/vesc_tool

Can you fix the desktop file please or better yet force the PKGBUILD to rename the output executable to /usr/bin/vesc_tool? That way is more future proof

I am getting:

zsh: no such file or directory: /usr/bin/vesc_tool

Any idea?

I switched to the mold linker on purpose to reduce the enormous link times (with LTO) of this project and get better error messages when the linking fails due to the patched buildscript. If you don't like that, use qmake -unset <flags> to remove it.

@SysGhost: Sorry for forgetting to remove the patch after I got it merged upstream.

I received the notification mail but overlooked it in the bulk of mails.

Trying to apply an already applied patch:

patching file vesc_tool.pro
patching file lzokay.cpp
Reversed (or previously applied) patch detected!  Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file lzokay.cpp.rej
==> ERROR: A failure occurred in prepare().
    Aborting...

Easily fixed by removing or commenting out the patch line for lzokay in the prepare function in PKGBUILD. A line that starts with "patch -d lzokay -i " ... Once disabled, it configures and builds fine.