[cygwin]Howto make a portable cygwin environment

I, have thoroughly emigrated to Linux, need a Linux-Like environment
to make things better in my PC-Architecture course, so I decide to
make a portable cygwin environment.

Because I have no portable devices, such as Flash Disk. I have to
upload the whole environment to internet for further downloading.

Here is WHAT I do to make such a portable cygwin environment.

1. cp the cygwin which is already installed when I used windows to a
work directory named $cygwin.
2. write a script to make a cygwin environment, such as where is the
/, /usr and /bin in windows
use $cygwin/bin/mount to make mount points on which the
$cygwin/bin/bash depends to make a work environment.

/etc/profile will be read when evoke bash with a --login parameter,
namely evoke a login bash shell

[fpga] Storing Quartus II projects under version control

reference at nios2wiki

Storing Quartus II projects under version control

There is no need to backup all files in a Quartus project to be able reproduce it. You have to store source files (so that you can modify the project) and final binary files (so that you can reproduce the system exactly).

NOTE: This is not the final list yet, but it works for most simple projects (the software part is still missing). You should still test a reconstruction of the project from this files.

Quartus II source files:

• project files:
  • project_name.qpf Quartus II project file
  • project_name.qsf Quartus constraint file (lists the hardware constraints defined for a project, from the used chip and pinout to timing constraints)
  • project_name.qws Quartus Window Settings ? (the configuration of the Quartus gui for the project, may be omitted)
• top level source files:
  • project_name.bdf Block diagram / Schematic file (top level schematic file, there may be many nested files)
  • project_name.vhd VHDL file (top level VHDL file)
  • project_name.v Verilog file (top level Verilog file)
• component source files:
  • component_name.bsf Block Symbol file (component symbol file)
  • component_name.vhd VHDL file (top level VHDL file)
  • component_name.v Verilog file (top level Verilog file)
• SOPC builder project source files (SOPC builder creates many VHDL or Verilog files, that you do not need to store)
  • sopc_project_name.ptf the list and configuration of components selected in the SOPC gui
  • sopc_project_name.bsf Block Symbol file (SOPC component symbol file, especially if you modified it)
• Board Description (if you created your own board, the list is incomplete!)
  • board_name/class.ptf
• software source files:
  • tbd

Quartus II binary files

• hardware binary files
  • project_name.sof SRAM Object File
• software binary files
  • tbd

Reconstructing a project from a subversion repository

Since the subversion repository contains only the necessary files, a procedure should be followed for reconstructing the full project from the repository.

1. Import the selected project from the subversion repository to the local drive.
2. Open the project in Quartus II.
3. Open the SOPC builder project and build it.
4. Build the Quartus II project and program the hardware into the FPGA.
5. Import the software part of the project into a NIOS IDE workplace.

References

Archiving SOPC Builder Projects http://www.altera.com/literature/hb/qts/qts_qii54017.pdf