Include_makefiles_with_bottom_up_scripts[=on|off – Altera Quartus II Scripting User Manual
Page 36
2–10
Chapter 2: Command-line Executables
quartus_cdb
Quartus II Scripting Reference Manual
© July 2013
Altera Corporation
Post-synthesis files
Post-fitting files
Generic files
--include_all_logiclock_regions_in_bottom_up_scripts[=on|off]
When this option is enabled, every generated Tcl script contains all of the top-level LogicLock regions.
Regions with logic not associated with the script's target partition act as placeholders and are empty. This
command helps describes for the lower-level project the way it fits into the final, top-level design.
The option is ignored if --include_logiclock_regions_in_bottom_up_scripts=off is used.
This option is enabled by default. Add the flag --include_all_logiclock_regions_in_bottom_up_scripts=off
to disable.
--include_design_partitions_in_bottom_up_scripts[=on|off]
When this option is enabled, generated Tcl scripts contain all relevant design partition assignments from
the top-level.
This option is enabled by default. Add the flag --include_design_partitions_in_bottom_up_scripts=off to
disable.
--include_global_signal_promotion_in_bottom_up_scripts[=on|off]
When this option is enabled, generated Tcl scripts contain commands that force any signals promoted to
'global' in the top-level to be promoted in the lower-level.
This option is enabled by default. Add the flag
--include_global_signal_promotion_in_bottom_up_scripts=off to disable.
--include_logiclock_regions_in_bottom_up_scripts[=on|off]
When this option is enabled, generated Tcl scripts contain the top-level LogicLock regions associated with
this partition. This helps ensure the lower-level project places its logic where the top-level project expects
it.
This option is enabled by default. Add the flag --include_logiclock_regions_in_bottom_up_scripts=off to
disable.
--include_makefiles_with_bottom_up_scripts[=on|off]
Option to generate makefiles for lower-level projects in addition to the Tcl scripts. One makefile is
generated for each lower-level project, for the top-level project and for the overall design (known as the
master_makefile). The master makefile simply invokes all other makefiles.