core/cmd/mkimage: clean up

This cleans up a few minor issues with the mkimage tool:
 - error logging now goes to stderr; it going to stdout made my life
   painful when debugging a build failure as the output got mangled by
   Bazel
 - repeated actions (copies, mkdirs) are now expressed less verbosely
 - flags are now declared in a more canonical way
 - flags are now named in a more canonical way (underscores vs. hyphens;
   these haven't been used anywhere in the build, so we're not breaking
   anything).

Test Plan: Refactor, no change behaviour (apart from stderr logging).

X-Origin-Diff: phab/D558
GitOrigin-RevId: 2531562acc46ec7aa0a6ac89b883dfd45cddcf82
1 file changed
tree: e0d24ad1acf54bc4ad85265cf5a8d4f62c2929a8
  1. build/
  2. core/
  3. scripts/
  4. third_party/
  5. .bazelignore
  6. .bazelrc
  7. BUILD
  8. nogo_config.json
  9. README.md
  10. WORKSPACE
README.md

Nexantic monorepo

This is the monorepo storing all of nexantic's internal projects and libraries.

Environment

We assume a Fedora host system provisioned using rW, and IntelliJ as the IDE.

For better reproducibility, all builds are executed in containers.

Usage

Spinning up: scripts/create_container.sh

Spinning down: scripts/destroy_container.sh

Running commands: scripts/run_in_container.sh <...>

Using bazel using a wrapper script: scripts/bin/bazel <...> (add to your local $PATH for convenience)

IntelliJ

This repository is compatible with the IntelliJ Bazel plugin. All commands run inside the container, and necessary paths are mapped into the container.

We check the entire .ijwb project directory into the repository, which requires everyone to use the latest version of both IntelliJ and the Bazel plugin, but eliminates manual setup steps.

The following steps are necessary:

  • Install Google's official Bazel plugin in IntelliJ.

  • Add the absolute path to your ~/.cache/bazel-nxt folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:

    -Dbazel.bep.path=/home/leopold/.cache/bazel-nxt

  • Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel. This is a wrapper that will execute Bazel inside the container.

  • Open the .ijwb folder as IntelliJ project.

  • Disable Vgo support for the project.

  • Run a non-incremental sync in IntelliJ

The plugin will automatically resolve paths for generated files.

If you do not use IntelliJ, you need to use the scripts/bazel_copy_generated_for_ide.sh script to copy files locally.