B E L K Q u i c k S t a r t G u i d e
v . 1 . 0 . 9
3.3.2.1 How BORA/BORAX project files are managed
Since a Vivado project for the Zynq device is composed by a lot
of files (including temporary and GUI-managed files), providing
the BORA/BORAX project files with the BELK is not considered
as an efficient and user-friendly solution, for two main reasons:
●
we should provide a compressed archive for each version
(updates, new features, bug fixes) of the project, wasting storage
space and download bandwidth, introducing redundancy and
complicating file management
●
there is no version control, which means that it's not possible to
track changes to the project files, making development and
release management complicated and error-prone
The best solution to these problems is that we create and
maintain a Git repository to store and track only the main files
of the Vivado project. Therefore, the developer can clone the
repository and keep it in sync with our modifications.
The following diagram shows how the solution works:
March, 2016
31/66
DAVE
Bora public
Git repository
Internet
DAVE
Bora
Development
Team
Git Push
1) Git Clone
2) Git Fetch/Pull
Vivado Design Suite
Customer local
Bora Git repository
Vivado
project
files
Xilinx SDK
Export
to
SDK
Zynq Development Server
Import/build
project
Keep git repo in sync with
modifications done in Vivado
