-
Notifications
You must be signed in to change notification settings - Fork 757
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[meson] delete meson.build files in favor of bazel #12449
Labels
Comments
This is partially accomplished in #12394, but it was determined it would be easier to remove all meson.build files at once, than to stage them (i.e., ROM build files first, then all sw/ after). |
timothytrippel
added
Priority:P1
Priority: high
and removed
Priority:P0
Priority: critical
labels
May 6, 2022
CC: @cfrantz @arunthomas As I mentioned earlier this week, this issue contains the list of items that must be addressed to delete meson from the repository. CCing you both for visibility. |
timothytrippel
added a commit
to timothytrippel/opentitan
that referenced
this issue
May 12, 2022
Meson will soon be removed from our project and replaced entirely with bazel (lowRISC#12449). This updates the the OTBN `gen-binaries.py` script to not rely on the presence of the `.env` file that was produced by the `meson_init.sh` script to provide locations to the RV32 toolchain. Instead, the `gen-binaries.py` script now uses environment variables to get the locations of the RV32 toolchain tools, which are populated via queries to bazel. This fixes lowRISC#12447. Signed-off-by: Timothy Trippel <[email protected]>
timothytrippel
added a commit
to timothytrippel/opentitan
that referenced
this issue
May 12, 2022
Meson will soon be removed from our project and replaced entirely with bazel (lowRISC#12449). This updates the the OTBN `gen-binaries.py` script to not rely on the presence of the `.env` file that was produced by the `meson_init.sh` script to provide locations to the RV32 toolchain. Instead, the `gen-binaries.py` script now uses environment variables to get the locations of the RV32 toolchain tools, which are populated via queries to bazel. This fixes lowRISC#12447. Signed-off-by: Timothy Trippel <[email protected]>
timothytrippel
added a commit
to timothytrippel/opentitan
that referenced
this issue
May 13, 2022
Meson will soon be removed from our project and replaced entirely with bazel (lowRISC#12449). This updates the the OTBN `gen-binaries.py` script to not rely on the presence of the `.env` file that was produced by the `meson_init.sh` script to provide locations to the RV32 toolchain. Instead, the `gen-binaries.py` script now uses environment variables to get the locations of the RV32 toolchain tools, which are populated via queries to bazel. This fixes lowRISC#12447. Signed-off-by: Timothy Trippel <[email protected]>
timothytrippel
added a commit
to timothytrippel/opentitan
that referenced
this issue
May 13, 2022
Meson will soon be removed from our project and replaced entirely with bazel (lowRISC#12449). This updates the the OTBN `gen-binaries.py` script to not rely on the presence of the `.env` file that was produced by the `meson_init.sh` script to provide locations to the RV32 toolchain. Instead, the `gen-binaries.py` script now uses environment variables to get the locations of the RV32 toolchain tools, which are populated via queries to bazel. This fixes lowRISC#12447. Signed-off-by: Timothy Trippel <[email protected]>
timothytrippel
added a commit
to timothytrippel/opentitan
that referenced
this issue
May 13, 2022
Meson will soon be removed from our project and replaced entirely with bazel (lowRISC#12449). This updates the the OTBN `gen-binaries.py` script to not rely on the presence of the `.env` file that was produced by the `meson_init.sh` script to provide locations to the RV32 toolchain. Instead, the `gen-binaries.py` script now uses environment variables to get the locations of the RV32 toolchain tools, which are populated via queries to bazel. This fixes lowRISC#12447. Signed-off-by: Timothy Trippel <[email protected]>
timothytrippel
added a commit
that referenced
this issue
May 13, 2022
Meson will soon be removed from our project and replaced entirely with bazel (#12449). This updates the the OTBN `gen-binaries.py` script to not rely on the presence of the `.env` file that was produced by the `meson_init.sh` script to provide locations to the RV32 toolchain. Instead, the `gen-binaries.py` script now uses environment variables to get the locations of the RV32 toolchain tools, which are populated via queries to bazel. This fixes #12447. Signed-off-by: Timothy Trippel <[email protected]>
timothytrippel
added a commit
to timothytrippel/opentitan
that referenced
this issue
Jun 10, 2022
This removes all `meson.build` files in favor of using Bazel as the OpenTitan build system. This fixes lowRISC#12449. Signed-off-by: Timothy Trippel <[email protected]>
Merged
timothytrippel
added a commit
to timothytrippel/opentitan
that referenced
this issue
Jun 10, 2022
This removes all `meson.build` files in favor of using Bazel as the OpenTitan build system. This fixes lowRISC#12449. Signed-off-by: Timothy Trippel <[email protected]>
timothytrippel
added a commit
that referenced
this issue
Jun 10, 2022
This removes all `meson.build` files in favor of using Bazel as the OpenTitan build system. This fixes #12449. Signed-off-by: Timothy Trippel <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Once the following issues have been addressed, all
meson.build
files can be removed (with minimal regressions):gen-binaries.py
's reliance onmeson_init.sh
script #12447@bitstreams
external repo fetch in offline (airgapped) mode #12455boringssl
andmundane
deps via sha256s #12531otbn_randomness
test in Bazel #12494Additionally the following items will need to be fixed after the meson deletion to cleanup some minor regressions:
lld
system requirement #12448 (temporary solution will work for the time being)sw/device/benchmarks/coremark
#12504The text was updated successfully, but these errors were encountered: