From e0271902d5c307f7599de5c5ff9f4790dde51702 Mon Sep 17 00:00:00 2001
From: Erik Kooistra <kooistra@astron.nl>
Date: Mon, 24 Nov 2014 14:17:06 +0000
Subject: [PATCH] More on zip files and RadioHDL view points.
---
tools/hdltool_readme.txt | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/tools/hdltool_readme.txt b/tools/hdltool_readme.txt
index 1cdda64d0d..28bc6392ae 100644
--- a/tools/hdltool_readme.txt
+++ b/tools/hdltool_readme.txt
@@ -525,9 +525,17 @@ g) regression test script
101) More ideas
-a) zip script
- - zip all required libraries for a certain level library --> useful for somebody who wants to reuse a library.
- - zip all tool environent code --> useful for somebody who wants touse our tool flow but not our HDL.
+a) zip scripts
+ A zip script can gather all sources that are needed for a particular RadioHDL view point, eg.
+
+ - zip all required libraries for a certain level library --> useful for somebody who wants to reuse a HDL library.
+ - zip all code necessary to run Python test cases on HW target --> useful for somebody who only wants to use the HW.
+ - zip all tool environent code --> useful for somebody who wants to use our tool flow but not our HDL.
+
+ Related to this is (how) can we more clearly divide up the RadioHDL/ directory to eg. reuse only parts of it and
+ to develop these in other locations/repositories (eg. GIT). Eg. the applications/ directory may not be needed or
+ even suitable in RadioHDL/ because applications could be kept elsewhere, even in another repository at another
+ institute.
b) support dynamic generation of IP
Very preliminary ideas:
--
GitLab