-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iio_scan_context_get_info_list Generating errors when no devices available #794
Comments
@tfcollins I can't reproduce. I built it from the exact same git commit, and it works fine on my ZedBoard (detects the local backend) and on my PC (detects my Pluto). |
Try it without a device or context available |
@tfcollins could you share the generated |
|
yeah, I get the same as @pcercuei
I don't see the error. |
but will add, when I build it with avahai off,
then I do see the error:
|
yeah, this happens because we tell you to find something on ip, and ip is built without DNS_SD support... So, this fixes it - I can make a PR if @pcercuei agrees with the fix.
|
@rgetz that's not the right fix. If you disable the local or USB backends you will get the same issue. |
Use CMake to give us a list of the backends available for scanning. This makes sure that the context scan won't fail by trying to scan from a backend that wasn't enabled. Fixes #794. Signed-off-by: Paul Cercueil <[email protected]>
yeah, this fixes things in a more general purpose way. Thanks |
Use CMake to give us a list of the backends available for scanning. This makes sure that the context scan won't fail by trying to scan from a backend that wasn't enabled. Fixes #794. Signed-off-by: Paul Cercueil <[email protected]>
This appeared within the last few days.
Running iio_info and python equivalent returns errors on scanning. Example with fresh ubuntu 20.04 docker image:
iio_info
Python
pyadi build: https://github.com/analogdevicesinc/pyadi-iio/runs/5251654994?check_suite_focus=true#step:5:64195
Bisecting breaking change: b058c69
The text was updated successfully, but these errors were encountered: