https://github.com/filmil/bazel_rules_vivado
https://github.com/filmil/bazel_rules_vivado
Last synced: about 1 month ago
JSON representation
- Host: GitHub
- URL: https://github.com/filmil/bazel_rules_vivado
- Owner: filmil
- License: apache-2.0
- Created: 2024-06-08T07:44:12.000Z (11 months ago)
- Default Branch: main
- Last Pushed: 2025-02-26T05:59:43.000Z (2 months ago)
- Last Synced: 2025-02-26T06:28:03.338Z (2 months ago)
- Language: Starlark
- Size: 86.9 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# bazel_rules_vivado: rules for the Xilinx Vivado tooling
This is not a stand-alone rules repository. It relies on
https://github.com/agoessling/rules_vivado, which builds a Docker container
out of a Vivado installation archive.
It uses an approach I developed for bazel exemplified in
https://github.com/filmil/bazel-rules-bid, which is able to execute a binary
in a docker container as a build action. This means you can have a portable
ephemeral Vivado installation for use in your bazel builds.
Unfortunately, I think it is not possible to distribute this docker container,
so you will need to make it yourself.
Once you do, you can install the prerequisite using:
```
bazel run //prerequisites:vivado -- path_to_the_image.tgz
```
This step will last a couple of hours. But, luckily, it should only be
needed once. The Vivado container is humongous, over 250GiB, so you need
plenty of disk space to make it work.
# Prior art
* https://github.com/agoessling/rules_vivado: this repository predates
`bazel_rules_vivado`. But, it also adopts a different approach, and requires
you to have a preinstalled Vivado instance.