Dan Nechita
Dan Nechita
libiio declares the variable iio_external_backend but intentionally does not define it, leaving the responsibility for the client code to provide its definition. So far, I thought of the following: Option...
I defined it as weak symbol and created a small test app that overrides it. Within the test app I can see the overridden version of the symbol but the...
Based on my tests, I am not getting this: `backend with index: 4 has name: custom-override-backend` but `backend with index: 4 has name: default-weak-backend` This happens when `-Wl,-Bsymbolic` flag is...
Closing this as the initial question has been answered.
I think this PR has reach its final state in terms of changes which include: - cmake will turn ON or OFF the relevant options when configuring for Tinyiiod. It's...
> I don't know if that is what you want to do or not? I wouldn't want to lose those older distributions. Additionally, the current implementation works properly without any...
Closing this as the purpose of these changes is unclear.
@buha thanks for putting together all these issues that users have encountered. They seem quite a lot and therefore I'm leaning toward enabling it by default.
> > rather than forcing this logic into all the applications - (refreshing things) - why not just do this inside libiio? (ie. - for this one special one -...
> When I was looking into it I was trying to make scan_type an attribute, so it would be read like the others (e.g., _raw) And then I tripped into...