feature: gr-iio #12
Open
feature: gr-iio #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feature: gr-iio
This brings in two new Docker containers that will be used by the continuous integration Docker containers for building GNU Radio. This allows a unified approach for dependancies required for
gr-iio🤓, and pinning a known working version of dependancies.A follow up pull request will allow bringing in the dependancies instead of building from source, such as the following example:
In the various containers we can just copy in the dependancies we need without building and this also gives a time saving on continuous integration builds as at the moment we do a compile from source each time.
In order for these to be used, they would need pushing to a Docker registry such as:
https://hub.docker.com/u/gnuradio
I have included some scripts that show this process of building and pushing to a Docker registry (left with comments, but the scripts can be used for local testing). But I cannot do this stage. I will happily work with someone on getting these pushed, and I am happy to maintain these going forward.
There are limited releases of:
https://github.com/analogdevicesinc/libiio
So should be easy to maintain if there was a version change.
I would need these pushing first before I can refactor the other containers.
The second container use the
COPYapproach for bringing inlibiiodependancies for buildinglibad9361-iioand this approach will be used in the follow up pull request for the continuous integration Docker containers but again this has the dependancy on the need to be pushed to a Docker registry.I have started this pull request for a larger discussion, but this is the first stage to refactoring some of the continuous integration Docker containers.
These containers I was using to test
gr-iiowith actual hardware and I have included notes on how to use these containers with actual hardware 😁, so they have been well tested before opening this pull request.Signed-off-by: Adam Horden [email protected]