Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
H
HDL
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
RTSD
HDL
Commits
16ed7784
Commit
16ed7784
authored
10 years ago
by
Eric Kooistra
Browse files
Options
Downloads
Patches
Plain Diff
To do: move build_dir_sim and build_dir_synth from hdllib.cfg to hdltool.cfg.
parent
6ed6463b
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
tools/hdltool_readme.txt
+5
-2
5 additions, 2 deletions
tools/hdltool_readme.txt
with
5 additions
and
2 deletions
tools/hdltool_readme.txt
+
5
−
2
View file @
16ed7784
...
@@ -577,7 +577,6 @@ f) Generate Quartus IP key
...
@@ -577,7 +577,6 @@ f) Generate Quartus IP key
- Using build_dir_synth is also sufficient/suitable to define the build subdirectory for IP generation.
- Using build_dir_synth is also sufficient/suitable to define the build subdirectory for IP generation.
g) hdltool.cfg per toolset
g) hdltool.cfg per toolset
. Is the hdltool.cfg necessary/useful at all?
. The model_tech_dir key in hdltool.cfg depends on the modelsim version that is defined in the toolset. The
. The model_tech_dir key in hdltool.cfg depends on the modelsim version that is defined in the toolset. The
model_tech_dir gives the path to the modelsim.ini that needs to be included in the mpf, because without the
model_tech_dir gives the path to the modelsim.ini that needs to be included in the mpf, because without the
IEEE and STD libraries are not known anymore after the mpf is loaded.
IEEE and STD libraries are not known anymore after the mpf is loaded.
...
@@ -596,9 +595,13 @@ g) hdltool.cfg per toolset
...
@@ -596,9 +595,13 @@ g) hdltool.cfg per toolset
model_tech_dir = /home/software/Mentor/10.4/modeltech
model_tech_dir = /home/software/Mentor/10.4/modeltech
Currently the 6.6c modelsim.ini is used even if Modelsim 10.4 is ran.
Currently the 6.6c modelsim.ini is used even if Modelsim 10.4 is ran.
. The build_dir_sim and build_dir_synth are defined in the hdllib.cfg and both set to $HDL_BUILD_DIR. It seems
better to define these keys in the hdltool.cfg, because currently all they are thesame in all hdllib.cfg and
with the possibility to define different hdltool.cfg there is already enough freedom.
Conclusion:
Conclusion:
- Keep hdltool.cfg, but define dedicated hdltool_<toolset>.cfg and add --toolset command line option.
- Is the hdltool.cfg necessary/useful at all? Yes. Keep hdltool.cfg, but define dedicated hdltool_<toolset>.cfg
and add --toolset command line option.
h) regression test script
h) regression test script
- To simulate all self-checking VHDL test benches and report the result.
- To simulate all self-checking VHDL test benches and report the result.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment