Obijuan
commented
3 years ago Ups! I forgot to leave a comment here. I am so sorry for the late response
It is not necesary to have a release for testing the latest changes in apio, just install the development version with this command:
sudo pip3 install -U git+https://github.com/FPGAwars/apio.git@develop#egg=apioSo, whenever someone make a change, they emits a pull-req and it is available after the merge, intallling apio with the previous command
Nevertheless, we will try to release apio as soon as possible. We still have to finish the support for the ulx and fomu boards
More information on apio develpment version can be found here:
https://github.com/FPGAwars/apio/wiki/Apio-development-version
pcossutta
This is a request, not an issue. Next month we are starting to use upduino3 in an online University course. It would be of great help to have the board supported in the apio release. As the board is currently supported on GitHub a new release would allow us to use apio without any modification. Is that possible ?
By the way I think that the usage of apio.ini should be different. If the board data where on it instead of only the label of the platform, one could provide a custom apio.ini to support a new board without the need to release a new version. I think that would also improve the usability of apio as well. I couldnt find an easy way to do this without modifying boards.json and given that every user possible have a different os or different python distribution, this is a difficult task to perform.