The past few days, I have been trying to get WaveForms up and Running on NixOS (Linux distro with declarative builds). So far, the dynamically linked libraries are working, including those from and for the Adept Runtime. The udev rules are also functional and the device is recognized as
Bus 005 Device 002: ID 1443:7003 Digilent Digilent USB Device
which seems to be the AD3 which I am using. However, when I try to connect to my device with WaveForms, the AD3 is not detected. I am now trying to figure out further hidden requirements of WaveForms / Adept that are required to connect to devices. Any help is appreciated and I am willing to share my nix derivation if anyone is interested.
It seems this issue is rather complex since the software comes in two parts:
These two parts of the software interface via a set of libraries contained by the Adept package. Each part itself has additional resources that it comes packaged with. So far, all dynamically linked executables are functional and the WaveForms GUI opens as intended. However, connecting to a device is not possible. Also, it should be noted that the software is only available as .deb packages. This poses the following questions:
- Which files do the programs require static read access to? Where do they have to be located and is it ok if they are linked?
- Does WaveForms require read access to shared resources that belong to Adept? How about the other way around?
- Which files do the programs require static write access to?
- Does either of both require access to certain system services?
- Do the two of them truly only interact via the libraries or are there other forms of interaction that need to be available?
- Are there any unmet non-linked dependencies or missing software?
I think I remember using Waveforms on the AUR a long time ago, might be worth looking into how they do it.
1 Like