In this lab you are advised not to share or archive your workspace simply by zipping it up and sending it off. In my FPGA designs at work the verilog designs are foten shared among two engineers while the software for the SOC FPGa desing is done by one of three software engineers. So it is very common to have mutiple peopleworkingon the same project and sharing the design envirnoment and porject come in handy.
Workspaces are just a container of software projects, and your preferences are user- and location-specific. If you simply copy the workspace to a different location in the system, it is not guaranteed to work.
Software projects, including board support packages, and software applications that you create in your workspace, can be shared with other team members or archived into a source control system. To do this, share or archive a collection of source files and SDK metadata files in the project directory. ''
This lab taught me how to:
• Create a complete project archive
• Create a new, duplicate project by importing your archive
• Create a new application, and import the sources for that application
In the first experiment you learn to the following steps to copy your entire project workspace so that it can be reproduced:
- Archive the project sources in an archive file
- Archive the Run/Debug configurations in an archive directory, if desired
- Archive debug breakpoints, if desired
- Preserve SDK (including repository settings) preference files, if desired
The second experiment involved restoring the the files archived in the first experiment. In the new workspace I was able to recreate and run the Hello_Zynq application as shown below.
