Installation of Waveforms on Linux amd64 runs into dependency problem

[Guest]

Hi,

 

I am trying to install Waveforms 3.17.1 on my Linux system, but it seems to depend on Adept version 2.26.1 or higher. However, the Adept version currently on download from the Digilent site is 2.21.3:
 

Preparing to unpack digilent.waveforms_3.17.1_amd64.deb ...
Unpacking digilent.waveforms (3.17.1) over (3.16.3) ...
dpkg: dependency problems prevent configuration of digilent.waveforms:
 digilent.waveforms depends on digilent.adept.runtime (>= 2.26.1); however:
  Version of digilent.adept.runtime on system is 2.21.3.

Best Sidney
 

[attila]

Hi @reddish

You can find the links to adept 2.26.1 at:

 

Edited October 22, 2021 by attila

[Guest]

Thanks. It would be useful if the standard download page on the Digilent site was also updated of course.

As a side question: did you guys ever consider to set up something like an APT repository for Adept and Waveforms? Or, even better, get them into Debian non-free?

Best Sidney

[attila]

Hi @reddish

Adept 2.26.1 will be officially released together (or before) the wf 3.17.1

We have thought about repo but not yet committed to, it would be another thing to maintain...

[Guest]

Hi Attila,

Hmm, on the official download page (https://digilent.com/shop/software/digilent-waveforms/) the version made available is already Waveforms 3.17.1.

I understand your hesitance to take on yet another deployment target, of course. I'm already very happy you guys provide proper linux support.

Best Sidney

[attila]

Hi @reddish

Thank you for the notification.

I didn't notice it is already released for public and also the download page is changed since I last visited it :)

[attila]

Hi @reddish

Regarding your question in private message, I reply here since it may be useful for other people too.

The FDwfEnumInfo info is not really needed for custom apps. It is for delay loaded "Remote Devices"... With custom apps the IP or Alias can be used for connection.
The other AMFM functions are only for the obsolete EExplorer...

The enum filtering is backward compatible.
You can still use device id for filtering, like FDwfEnum(devidDiscovery2)
The filter meaning only changes when MSbit (Type) is used, like FDwfEnum(enumfilterType | enumfilterUSB)

Edited October 22, 2021 by attila