Adding Travis-CI which builds gateware #50
Closed
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
mithro
force-pushed
the
travis-xilinx
branch
2 times, most recently
from
186a23e
to
065af17
Compare
mithro
force-pushed
the
travis-xilinx
branch
from
065af17
to
de817bd
Compare
(So impact gets included in the package.)
mithro
force-pushed
the
travis-xilinx
branch
from
de817bd
to
745b3b8
Compare
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.
Fixes #8.
This stuff is based of the artiq stuff at https://github.com/m-labs/artiq and uses a similar method of making a cut back Xilinx ISE which is then encrypted and only made avaliable to the CI system. Because of the stripped back nature of the Xilinx ISE, changes can cause build failures if they make ISE require new files that were not previously touched. The .travis/package-xilinx.sh script can be used to recreate the package from a full ISE install.
Travis continues to use the same "quick setup scripts" we recommend people run to get up and running. It is important to keep things this way so that we have testing of the setup instructions.
As the gateware takes significantly longer than the previous firmware builds, each target now builds on a separate machine.