vdct2template
Converts EPICS vdct templates to pure msi compatible EPICS db templates
This tool is designed to modify an EPICS support module in order to remove its dependency on the vdct tool. This is useful for support modules that we want to build with the upstream vanilla EPICS base that does not include vdct.
| What | Where |
|---|---|
| Source | https://github.com/epics-containers/vdct2template |
| PyPI | pip install vdct2template |
| Releases | https://github.com/epics-containers/vdct2template/releases |
Installation
To install the latest release from PyPI, create a virtual environment and pip install like this:
python -m venv venv
source venv/bin/activate
pip install vdct2template
Usage
$ vdct2template --help
Usage: vdct2template [OPTIONS] FOLDER
VDCT to template conversion function.
• This function assumes that all referenced VDCT files in the expand() blocks will be
in the same folder.
• We can use the builder.py file to check for direct references to template files Use
--no-use-builder to disable this feature. Direct references to a template file is an
error because we need to modify all macro names to add a _ prefix in templated files.
• Files referenced in expand() blocks will have their macro names updated to all have a
_ prefix, because MSI does not support substituting a macro with it's own name and
passing a default. This is a workaround to that limitation.
• The original expands() block is replaced with a series of substitute MSI directives
and an include MSI directive.
• The resulting set of templates can be expanded natively by MSI without the need for
VDCT.
• The DB files created by such an expansion should be equivalent to the original VDCT
generated ones.
╭─ Arguments ────────────────────────────────────────────────────────────────────────────╮
│ * folder DIRECTORY folder of vdb files to convert to template files. │
│ [default: None] │
│ [required] │
╰────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Options ──────────────────────────────────────────────────────────────────────────────╮
│ --version Print the version and exit │
│ --use-builder --no-use-builder Use the builder.py file to look for │
│ direct references to template files. │
│ [default: use-builder] │
│ --builder FILE Path to the builder file. │
│ [default: None] │
│ --help Show this message and exit. │
╰────────────────────────────────────────────────────────────────────────────────────────╯
Metadata
Release files for vdct2template 1.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| vdct2template-1.0.4.tar.gz | 306.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vdct2template-1.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 323.5 kB
Release files / vdct2template-1.0.4.tar.gz
| Download URL | vdct2template-1.0.4.tar.gz |
|---|---|
| Size | 306.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eac2625348e381f67275c9c5de30f800ba52fba89960eadb893b2bc32e3f7975
|
|
BLAKE2b-256 checksum How to use checksums |
d03d81422a1bcd13ae55f714a8fe10d99a8ecd3fbe23075e7103c7799488ff44
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / vdct2template-1.0.4-py3-none-any.whl
| Download URL | vdct2template-1.0.4-py3-none-any.whl |
|---|---|
| Size | 17.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f38c11ec1df557c7346223f8253ae72fc7d6ac0d3b5bccde603027b9bae1848
|
|
BLAKE2b-256 checksum How to use checksums |
1fb2074c6cf3c88703cef7fbe7a8bd22190fcab62c8a0f94bc4669c14c57f2c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for vdct2template 1.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.