xactflow-archidesc 0.1.0__tar.gz

xactflow_archidesc-0.1.0/LICENSE

@@ -0,0 +1,164 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

xactflow_archidesc-0.1.0/PKG-INFO

@@ -0,0 +1,186 @@
+Metadata-Version: 2.4
+Name: xactflow-archidesc
+Version: 0.1.0
+Summary: XactFlow importer plugin that serializes an architecture description into an ipxact.Design.
+Author: Maxime Travaillard
+License-Expression: LGPL-3.0-only
+Project-URL: Repository, https://github.com/IP-XACT/XactFlow-archidesc
+Project-URL: Issues, https://github.com/IP-XACT/XactFlow-archidesc/issues
+Keywords: IP-XACT,IEEE 1685,XML,Compiler,XactFlow,Architecture,Design,Importer
+Classifier: Development Status :: 3 - Alpha
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Scientific/Engineering
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: xactflow
+Requires-Dist: ipxact-compiler
+Provides-Extra: dev
+Requires-Dist: pytest; extra == "dev"
+Requires-Dist: xactflow-design; extra == "dev"
+Dynamic: license-file
+
+# xactflow-archidesc
+
+A [XactFlow](https://github.com/IP-XACT/XactFlow) importer plugin that turns a design described
+in a Python script (which IPs it uses, and how they are connected) into an `ipxact.Design` object,
+built on [`ipxact-compiler`](https://github.com/IP-XACT/ipxact-compiler)'s
+[IEEE 1685-2022](https://standards.ieee.org/ieee/1685/10307/) object model.
+
+IP-XACT `design` files are not made to be handwritten. With this package, a short script lists
+the IP instances, the bus connections between them, and any direct signal connections. The
+importer runs the script and returns the `Design`, which XactFlow's `elaborate()` can then check
+against the IP-XACT rules.
+
+The full description of the format is in
+[`doc/python-design-description.md`](doc/python-design-description.md). It describes the tool
+as it is meant to work once finished, so the current version can differ from it in small ways.
+The differences known today are listed in [Known limitations](#known-limitations).
+
+## Installation
+
+```bash
+pip install xactflow-archidesc
+```
+
+For local development, `requirements-dev.txt` overrides `ipxact-compiler`, `xactflow` and
+`xactflow-design` to local installations. It can be modified to adapt the paths or to keep any
+of them on PyPI.
+
+```bash
+pip install -r requirements-dev.txt -e .
+```
+
+Requires Python >= 3.9.
+
+## Usage
+
+A design script builds a `Design` from an IP library and keeps it in a module-level variable
+named `design`:
+
+```python
+from pathlib import Path
+
+from xactflow import Library
+from xactflow_archidesc import Design
+
+library = Library.scan(Path(__file__).parent / "ip")
+design = Design("example.org:soc:example:0.1", library)
+
+cpu = design.add_ip("cpu", "example.org:ip:cpu:1.0", transforms=["tmrg"])
+uart = design.add_ip("uart", "example.org:ip:uart:1.0", parameters={"BAUDRATE": 115200})
+timer = design.add_ip("timer", "example.org:ip:timer:1.0")
+debug = design.add_ip("debug", "example.org:ip:debug_module:1.0")
+bus = design.add_ip("bus", "example.org:ip:interconnect:1.0")
+
+design.connect_bus(cpu, bus)
+design.connect_bus(bus.bus("m0"), uart, base_addr=0x4001_0000, size=0x1000)
+design.connect_bus(bus, timer, base_addr=0x4002_0000, size=0x1000)
+
+design.connect(debug.debug_req_o, cpu.debug_req_i)
+design.connect(cpu.debug_resp_o, debug.debug_resp_i)
+```
+
+A runnable version of this script, with its IP library, is in
+[`tests/fixtures/soc.py`](tests/fixtures/soc.py).
+
+In short:
+
+- `add_ip(name, vlnv, ...)` adds an IP instance, with optional `parameters` overrides and
+  `transforms`.
+- `connect_bus(a, b, ...)` connects a bus interface of `a` to one of `b`. It picks them by
+  itself, or uses the one named with `instance.bus("name")`. `base_addr`/`size` place a target
+  in the address map.
+- `connect(source, target)` connects two ports. `instance.some_port` is short for
+  `instance.port("some_port")`.
+
+Each call checks its arguments right away, so a mistake is reported on the line that made it.
+All the details are in [the format description](doc/python-design-description.md#the-design-object).
+
+Once installed, the importer registers itself under the `xactflow.importers` entry point group
+as `archidesc`, so it runs as a XactFlow CLI command. With `xactflow-design` installed too,
+`--then` hands the result straight to that exporter. To try it on the example of this repo,
+create a virtual environment and install the package in it first. The `xactflow` command only
+exists inside that environment, so activate it again in each new terminal:
+
+```bash
+python3 -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+xactflow archidesc tests/fixtures/soc.py --then design --output out/
+```
+
+This writes `out/example.xml`, named after the design's VLNV name.
+
+Or as a library, for example to elaborate the design first:
+
+```python
+from pathlib import Path
+
+from xactflow import Library, elaborate
+from xactflow_archidesc import ArchiDescImporter
+from xactflow_design import DesignExporter
+
+design = ArchiDescImporter().import_(Path("soc.py"))
+elaborated = elaborate(design, Library.scan("ip"))
+DesignExporter().export(design, Path("out"))
+```
+
+The script runs like `python soc.py` would: a helper module next to it can be imported, and a
+relative path in it is read from the current folder. `Path(__file__).parent` gives paths
+that do not depend on where the command is run from. The importer takes no options.
+
+## Design notes
+
+- **Vendor extensions.** Two things this format records have no place in IP-XACT, so they are
+  written as vendor extensions in the `https://github.com/IP-XACT/XactFlow` namespace:
+  `<xactflow:transforms>` on a component instance, listing the transformations in order, and
+  `<xactflow:addressMapping baseAddr="..." size="..."/>` on the target side of a bus
+  connection (a target or mirrored initiator interface).
+- **Transformations are not applied here.** A separate tool, a transformer, reads
+  `<xactflow:transforms>`, applies the transformations and returns the changed `Design`.
+- **Parameter overrides follow the standard.** Only a parameter with a `parameterId` and
+  `resolve="user"` can be overridden. The standard says an `immediate` parameter (the default)
+  cannot be changed through configuration.
+- **Connection names are unique.** A bus connection is named `<a>_to_<b>` and a port connection
+  `<instance>_<port>_to_<instance>_<port>`. A number is added when a name is already taken, by
+  any kind of connection.
+- **Monitors.** Connecting a monitor interface adds a `monitorInterconnection`. The interface it
+  watches stays free for a normal connection.
+
+## Known limitations
+
+- `connect_bus` compares the bus VLNV of the two interfaces, but not the parameter values set
+  on the bus type (a data width, for example). Comparing them needs XactFlow to evaluate
+  those values first. This should be changed in a future update.
+- XactFlow's `elaborate()` does not use the parameter overrides from `add_ip` yet. They are
+  written to the design and exported, but not applied during elaboration.
+- `connect` checks direction only for wire ports. Two transactional or two structured ports
+  are connected with no further check, only a mix of the two kinds is refused.
+- `connect` does not compare port widths.
+- A design describes one level only. Hierarchical designs, a real address mapping (instead of
+  the `addressMapping` placeholder) and protocol bridges are not handled yet, see the open
+  questions at the end of [the format description](doc/python-design-description.md).
+
+## Development
+
+```bash
+python3 -m venv .venv
+source .venv/bin/activate
+pip install -r requirements-dev.txt -e .
+pytest
+```
+
+The tests use a small IP library in `tests/fixtures/library`. `tests/test_end_to_end.py` runs
+the example script through the importer, elaborates the result, exports it with
+`xactflow-design` and reads the file back.
+
+## License
+
+LGPL-3.0. See [LICENSE](LICENSE).

xactflow_archidesc-0.1.0/README.md

@@ -0,0 +1,157 @@
+# xactflow-archidesc
+
+A [XactFlow](https://github.com/IP-XACT/XactFlow) importer plugin that turns a design described
+in a Python script (which IPs it uses, and how they are connected) into an `ipxact.Design` object,
+built on [`ipxact-compiler`](https://github.com/IP-XACT/ipxact-compiler)'s
+[IEEE 1685-2022](https://standards.ieee.org/ieee/1685/10307/) object model.
+
+IP-XACT `design` files are not made to be handwritten. With this package, a short script lists
+the IP instances, the bus connections between them, and any direct signal connections. The
+importer runs the script and returns the `Design`, which XactFlow's `elaborate()` can then check
+against the IP-XACT rules.
+
+The full description of the format is in
+[`doc/python-design-description.md`](doc/python-design-description.md). It describes the tool
+as it is meant to work once finished, so the current version can differ from it in small ways.
+The differences known today are listed in [Known limitations](#known-limitations).
+
+## Installation
+
+```bash
+pip install xactflow-archidesc
+```
+
+For local development, `requirements-dev.txt` overrides `ipxact-compiler`, `xactflow` and
+`xactflow-design` to local installations. It can be modified to adapt the paths or to keep any
+of them on PyPI.
+
+```bash
+pip install -r requirements-dev.txt -e .
+```
+
+Requires Python >= 3.9.
+
+## Usage
+
+A design script builds a `Design` from an IP library and keeps it in a module-level variable
+named `design`:
+
+```python
+from pathlib import Path
+
+from xactflow import Library
+from xactflow_archidesc import Design
+
+library = Library.scan(Path(__file__).parent / "ip")
+design = Design("example.org:soc:example:0.1", library)
+
+cpu = design.add_ip("cpu", "example.org:ip:cpu:1.0", transforms=["tmrg"])
+uart = design.add_ip("uart", "example.org:ip:uart:1.0", parameters={"BAUDRATE": 115200})
+timer = design.add_ip("timer", "example.org:ip:timer:1.0")
+debug = design.add_ip("debug", "example.org:ip:debug_module:1.0")
+bus = design.add_ip("bus", "example.org:ip:interconnect:1.0")
+
+design.connect_bus(cpu, bus)
+design.connect_bus(bus.bus("m0"), uart, base_addr=0x4001_0000, size=0x1000)
+design.connect_bus(bus, timer, base_addr=0x4002_0000, size=0x1000)
+
+design.connect(debug.debug_req_o, cpu.debug_req_i)
+design.connect(cpu.debug_resp_o, debug.debug_resp_i)
+```
+
+A runnable version of this script, with its IP library, is in
+[`tests/fixtures/soc.py`](tests/fixtures/soc.py).
+
+In short:
+
+- `add_ip(name, vlnv, ...)` adds an IP instance, with optional `parameters` overrides and
+  `transforms`.
+- `connect_bus(a, b, ...)` connects a bus interface of `a` to one of `b`. It picks them by
+  itself, or uses the one named with `instance.bus("name")`. `base_addr`/`size` place a target
+  in the address map.
+- `connect(source, target)` connects two ports. `instance.some_port` is short for
+  `instance.port("some_port")`.
+
+Each call checks its arguments right away, so a mistake is reported on the line that made it.
+All the details are in [the format description](doc/python-design-description.md#the-design-object).
+
+Once installed, the importer registers itself under the `xactflow.importers` entry point group
+as `archidesc`, so it runs as a XactFlow CLI command. With `xactflow-design` installed too,
+`--then` hands the result straight to that exporter. To try it on the example of this repo,
+create a virtual environment and install the package in it first. The `xactflow` command only
+exists inside that environment, so activate it again in each new terminal:
+
+```bash
+python3 -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+xactflow archidesc tests/fixtures/soc.py --then design --output out/
+```
+
+This writes `out/example.xml`, named after the design's VLNV name.
+
+Or as a library, for example to elaborate the design first:
+
+```python
+from pathlib import Path
+
+from xactflow import Library, elaborate
+from xactflow_archidesc import ArchiDescImporter
+from xactflow_design import DesignExporter
+
+design = ArchiDescImporter().import_(Path("soc.py"))
+elaborated = elaborate(design, Library.scan("ip"))
+DesignExporter().export(design, Path("out"))
+```
+
+The script runs like `python soc.py` would: a helper module next to it can be imported, and a
+relative path in it is read from the current folder. `Path(__file__).parent` gives paths
+that do not depend on where the command is run from. The importer takes no options.
+
+## Design notes
+
+- **Vendor extensions.** Two things this format records have no place in IP-XACT, so they are
+  written as vendor extensions in the `https://github.com/IP-XACT/XactFlow` namespace:
+  `<xactflow:transforms>` on a component instance, listing the transformations in order, and
+  `<xactflow:addressMapping baseAddr="..." size="..."/>` on the target side of a bus
+  connection (a target or mirrored initiator interface).
+- **Transformations are not applied here.** A separate tool, a transformer, reads
+  `<xactflow:transforms>`, applies the transformations and returns the changed `Design`.
+- **Parameter overrides follow the standard.** Only a parameter with a `parameterId` and
+  `resolve="user"` can be overridden. The standard says an `immediate` parameter (the default)
+  cannot be changed through configuration.
+- **Connection names are unique.** A bus connection is named `<a>_to_<b>` and a port connection
+  `<instance>_<port>_to_<instance>_<port>`. A number is added when a name is already taken, by
+  any kind of connection.
+- **Monitors.** Connecting a monitor interface adds a `monitorInterconnection`. The interface it
+  watches stays free for a normal connection.
+
+## Known limitations
+
+- `connect_bus` compares the bus VLNV of the two interfaces, but not the parameter values set
+  on the bus type (a data width, for example). Comparing them needs XactFlow to evaluate
+  those values first. This should be changed in a future update.
+- XactFlow's `elaborate()` does not use the parameter overrides from `add_ip` yet. They are
+  written to the design and exported, but not applied during elaboration.
+- `connect` checks direction only for wire ports. Two transactional or two structured ports
+  are connected with no further check, only a mix of the two kinds is refused.
+- `connect` does not compare port widths.
+- A design describes one level only. Hierarchical designs, a real address mapping (instead of
+  the `addressMapping` placeholder) and protocol bridges are not handled yet, see the open
+  questions at the end of [the format description](doc/python-design-description.md).
+
+## Development
+
+```bash
+python3 -m venv .venv
+source .venv/bin/activate
+pip install -r requirements-dev.txt -e .
+pytest
+```
+
+The tests use a small IP library in `tests/fixtures/library`. `tests/test_end_to_end.py` runs
+the example script through the importer, elaborates the result, exports it with
+`xactflow-design` and reads the file back.
+
+## License
+
+LGPL-3.0. See [LICENSE](LICENSE).

xactflow_archidesc-0.1.0/pyproject.toml

@@ -0,0 +1,58 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "xactflow-archidesc"
+dynamic = ["version"]
+description = "XactFlow importer plugin that serializes an architecture description into an ipxact.Design."
+readme = "README.md"
+license = "LGPL-3.0-only"
+license-files = ["LICENSE"]
+authors = [
+    { name = "Maxime Travaillard"},
+]
+requires-python = ">=3.9"
+dependencies = [
+    "xactflow",
+    "ipxact-compiler",
+]
+keywords = [
+    "IP-XACT", "IEEE 1685", "XML", "Compiler",
+    "XactFlow", "Architecture", "Design", "Importer",
+]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3 :: Only",
+    "Programming Language :: Python :: 3.9",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Topic :: Scientific/Engineering",
+]
+
+[project.urls]
+Repository = "https://github.com/IP-XACT/XactFlow-archidesc"
+Issues = "https://github.com/IP-XACT/XactFlow-archidesc/issues"
+
+[project.optional-dependencies]
+dev = [
+    "pytest",
+    # For the end-to-end test, exporting to XML for visual verification.
+    "xactflow-design",
+]
+
+[project.entry-points."xactflow.importers"]
+archidesc = "xactflow_archidesc:ArchiDescImporter"
+
+[tool.setuptools.dynamic]
+version = {attr = "xactflow_archidesc.__version__"}
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+xactflow_archidesc = ["py.typed"]

xactflow_archidesc-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

xactflow_archidesc-0.1.0/src/xactflow_archidesc/__init__.py

@@ -0,0 +1,44 @@
+__version__ = "0.1.0"
+
+import runpy
+import sys
+from pathlib import Path
+
+import ipxact
+from xactflow import Importer
+
+from .design import BusInterfaceRef, Design, IPInstance, PortRef
+
+
+class ArchiDescImporter(Importer):
+    """Runs a Python design description script and returns the ipxact.Design it describes.
+
+    The script must define a module-level variable named `design`, holding a Design. It runs
+    like `python script.py` would: its own folder is importable while it runs.
+    """
+
+    name = "archidesc"
+
+    def import_(self, source_path: Path, **options: object) -> ipxact.Design:
+        if options:
+            raise ValueError(f"the archidesc importer takes no options, got: {', '.join(options)}")
+        source_path = Path(source_path)
+        if not source_path.is_file():
+            raise ValueError(f"{source_path} is not a file")
+        sys.path.insert(0, str(source_path.parent))
+        try:
+            namespace = runpy.run_path(str(source_path))
+        finally:
+            sys.path.remove(str(source_path.parent))
+        if "design" not in namespace:
+            raise ValueError(f"{source_path} must define a module-level variable 'design'")
+        design = namespace["design"]
+        if not isinstance(design, Design):
+            kind = type(design)
+            raise ValueError(
+                f"{source_path}: 'design' must be a xactflow_archidesc.Design, got {kind.__module__}.{kind.__qualname__}"
+            )
+        return design.build()
+
+
+__all__ = ["__version__", "ArchiDescImporter", "BusInterfaceRef", "Design", "IPInstance", "PortRef"]