Altera Quartus II Scripting - Manual (Page 37)

Chapter 2: Command-line Executables 2–11
quartus_cdb
© July 2013 Altera Corporation Quartus II Scripting Reference Manual
Makefiles are designed to work with GNU make and support the '-j' option which allows parallel
compilation of the lower-level projects. The master makefile is all that needs to be called by the user to
ensure the lower-level projects are up to date and that the top-level project has imported the latest versions
of the lower-level projects. You can invoke the master makefile as follows (you must not turn off
--include_project_creation_in_bottom_up_scripts for this to work without modification):
gnumake -f master_makefile.mak -j2
<The '-j2' means there are 2 processors to use.>
Makefiles are placed in the directory of the project they control if project creation is enabled and
appropriate directories are automatically filled in. If you elect not to have the tool create projects for you,
all makefiles are placed in the specified output directory and the user must fill in the directory variables at
the top of each makefile so that the tool knows where the lower-level projects can be found. In both cases
you must add the source file dependencies for each lower-level project's makefile if maintainance of the
project after initial compilation is desired. By default no dependencies are created (other than one on the
auto-generated Tcl script for that partition) and so after the first c ompilation, the rule is be up to date.
By default, makefile generation is enabled. Add the flag --include_makefiles_with_bottom_up_scripts=off
to disable.
--include_pin_locations_in_bottom_up_scripts[=on|off]
When this option is enabled, generated Tcl scripts contain commands that lock any lower-level pins
connected directly to IOs in the top-level to the IO location they were placed at in the top-level. This helps
keep a consistent pin placement amongst projects.
This option is enabled by default. Add the flag --include_pin_locations_in_bottom_up_scripts=off to
disable.
--include_project_creation_in_bottom_up_scripts[=on|off]
When this option is enabled, generated Tcl scripts contain commands to create the lower-level projects if
the projects do not exist. The tool creates projects in subdirectories under the output directory, named
according to name of the corresponding partition.
By default, project creation is enabled. Add the flag --include_project_creation_in_bottom_up_scripts=off
to disable.
--include_timing_assignments_in_bottom_up_scripts[=on|off]
When this option is enabled, generated Tcl scripts contain all relevant timing assignments from the
top-level.
This option is enabled by default. Add the flag --include_timing_assignments_in_bottom_up_scripts=off
to disable.
--include_virtual_input_pin_timing_in_bottom_up_scripts[=on|off]
When this option is enabled, generated Tcl scripts contain INPUT_MAX_DELAY to constrain all paths to
the newly created virtual input pins (see --include_virtual_pins_in_bottom_up_scripts). The value for this
option is the inter-partition delay of paths driving the virtual inputs. For more information about the
meaning of theseassignments, please see the Quartus II Help topics relating to INPUT_MAX_DELAY.
The option is ignored if --include_virtual_pins_in_bottom_up_scripts=off is used.
If you use this option, you must also specify the delay (in nanoseconds) to be used in the constraints with
the --bottom_up_scripts_virtual_input_pin_delay option.