On FPGA Developer AMI use the correct vivado version #167
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.
This is to enable having both vivado and sdx installed in the AMI
so can use both the master and prelease branches which use different
versions of vivado.
Use module load to use the correct vivado version based on the HDK version.
Save the vivado version used to build the models.
Rebuild the models if they were built with the wrong vivado version.
Add a lock file to prevent multiple process from trying to build the
models at the same time, potentially with different vivado versions.
This requires procmail to be installed otherwise the lockfile isn't created/used.
Merged changes from prelease.
Not downloading the shell dcp from S3.
Leaving that the same.
This shouldn't be an issue when switching between prelease and master
because they use different shell versions.