Instead of using synth_top_level_entity implicitely it is more clear to have...

Instead of using synth_top_level_entity implicitely it is more clear to have an explicit quartus_create_qpf and quartus_create_qsf key to define this.

tools/hdltool_readme.txt

@@ -486,14 +486,16 @@ b) quartus_config.py command line arguments:
    
    Instead of the --compile option it is also an option to define a separate quartus_compile.py script.
    
-c) quartus_* keys
-   The quartus_* keys are now source oriented. Instead it may be better to redefine thme as target oriented. Eg. a
-   quartus_qsf key that defines to create a qsf file using the intormation listed in the values.
+c) quartus_* keys and synth_top_level_entity
+   . The quartus_* keys are now source oriented. Instead it may be better to redefine thme as target oriented. Eg. a
+     quartus_create_qsf key that defines to create a qsf file using the intormation listed in the values.
+   . The synth_top_level_entity enforces the creation of a qpf and qsf. This kind of hidden behavior is not so nice.
+     Instead it is more clear to have an explicit quartus_create_qpf and quartus_create_qsf key to define this.
    
 d) *_copy_files keys
-   - The copy_files() method in hdl_config.py currently uses shutil.rmtree(buildPath), this is probably too risky and
+   . The copy_files() method in hdl_config.py currently uses shutil.rmtree(buildPath), this is probably too risky and
      needs to be made more save to avoid that accidentally some wrong dir tree is removed.
-   - The source and destination directory definition needs to be made somewhat more clear. The path can be absolute or
+   . The source and destination directory definition needs to be made somewhat more clear. The path can be absolute or
      relative. The relative path can be from hdllib.cfg location in SVN or from the build dir. The direction van be
      from build dir to dir in SVN or vice versa, or to any directory location.