Arch Linux User Repository

Besides this package, which compiles the source code, I have built another AUR package, which provides a binary compiled by me.
Maybe it is interesting for some of you to use the already compiled version:

https://aur.archlinux.org/packages/profex-bin

In most cases, an installation of BGMN and the BGMN Structure and Device Templates will be necessary. Please install bgmn-bin before starting Profex so that it can locate and import the BGMN files.

Hmm.. interesting. I need to try the different installation ways to watch out for any differences. This PKGBUILD doesn't copy any files to ~/.local/share/doebelin.org/Profex5/

Edit 1:

The files and folders in question depend on the BGMN Stuff. Its a different program which needs to be installed. You can do it with https://aur.archlinux.org/packages/bgmn-bin But that only installs the binary and doesn't copy other stuff.

Additionally there are Structure and Device Templates as a separate download on the profex website. I could add them to this aur package but since its the BGMN stuff, I think it should be part of the bgmn aur package..

Edit 2:

I added the Template to the BGMN aur package. If profex finds the BGMN files on its initial start, it imports the files and everything works as expected!

I think this is not a program‑working issue; I’m not even sure it’s a problem with my specific setup, but when compiling the package or installing the binary version, the directories under /home/user/.local/share/doebelin.org/Profex5/—specifically Devices, Structures, and Presets—are empty. They contain no files that normally appear when using the installation script from the Profex website.

Besides this package, which compiles the source code, I have built another AUR package, which provides a binary compiled by me.
Maybe it is interesting for some of you to use the already compiled version:

https://aur.archlinux.org/packages/profex-bin

In most cases, an installation of BGMN and the BGMN Structure and Device Templates will be necessary. Please install bgmn-bin before starting Profex so that it can locate and import the BGMN files.

Changes in other programs have resulted in the program no longer compiling. It was therefore not possible to update to version 5.2.9.
The developer of Profex has already developed a fix for version 5.3.0 and sends me the needed includes:

#ifdef __GNUC__
#include "unistd.h"
#elif __clang__
#include "unistd.h"
#elif _MSC_VER
#include "io.h"
#endif

I added it to the 3 files:

• gzlib.c.new
• gzread.c.new
• gzwrite.c.new

and replace the existing files in zlib.

Thank you @henkm, I changed the PKGBUILD to your suggestion, works flawlessly for me.

And yes you are right, the binaries are listed as processes when those functions are selected in the main program.

From what I can tell, they are the functionality behind the electron density map (profexed), scan trace (profexst) and waterfall plot (profexwp). At least, without the extra executables those don't work. (You find them in the tools drop-down menu).

What is the function of those other executables? Do they link to some functionality in the main program?

I'll look into it. But your addition looks good, in the build documentation they do something similar:

sudo cp bin/profex* /usr/local/bin

Not much of a problem, I had 5.0.1-1 installed so auracle keeps nagging that there's an update, then makepkg quitting as the package is up to date. More a nuisance than a problem and should be fixed by updating the PKGBUILD. Thanks.

Edit to add: Three more executables are built but not installed: profexed, profexst and profexwp. There are no doubt better ways but changing the last lines of PKGBUILD to

mkdir "${pkgdir}/usr/bin"
install -Dm755 bin/* "${pkgdir}/usr/bin" 

did the trick for me

Yes, i pushed the commit to fast, so that the .srcinfo doesn't get the change. It should be pkgrel=1 in both files, since there was only one 5.0.1 release. Changing the pkgrel back to 1 in the .srcinfo could create issues, so I'll set it to 2 in PKGBUILD. But there shouldn't be a problem with updating right now or is there a problem on your side?