iio_attr: Fatal: program compiled against libxml 20 using libxml 2

No libxml.dll on computer. Search found several copies of libxml2.dll and libxml2-2.dll and one libxml_plugin.dll

Can you please see here:  RE: Problems using ADALM-PLUTO in python 

Can you try to temporarily rename the libxml2.dll in the Windows\System32 folder and reinstall libiio?

-Michael

The only reason I upgraded my Pluto fw and libiio was that I had downloaded a program (SATSAGEN, wonderful work) that called out fw 0.31, so I thought I'd upgrade (I had fw 0.30). I've just now downgraded back to fw 0.30 and libiio 0.21 because I found that SATSAGEN works ok with that.. BUT to get rid of the error and warning messages I had to UNINSTALL libiio and reinstall. Changing the names of libxml, libxml2, libiio,..... wasn't enough. I hate to gripe about Pluto since it's amazing for the price, but I find the fumbling and learning curve with the software one step forward 7/8 steps back. I write C code with MinGW, and with libiio 0.21 I see the libiio.dll.a file that I need with that. I don't see that file in later revs. I'll stay with the versions I have unless I must change. I thought that I had to change to use SATSAGEN, but I was wrong.

Libiio is typical backward compatible. To my knowledge we never broke this compatibility. The issue is that the installer never overwrites existing files in the system folder. And I think that's for good reason. Honestly I'm not sure that the conflicting dll was created by a pervious install.

We need to check why the libiio.dll.a is not longer packaged.

Sorry for the inconvenience.

-Michael

Libiio is typical backward compatible. To my knowledge we never broke this compatibility. The issue is that the installer never overwrites existing files in the system folder. And I think that's for good reason. Honestly I'm not sure that the conflicting dll was created by a pervious install.

We need to check why the libiio.dll.a is not longer packaged.

Sorry for the inconvenience.

-Michael