Skip to content
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

Vermaete/kas #1316

Open
wants to merge 4 commits into
base: build
Choose a base branch
from
Open

Vermaete/kas #1316

wants to merge 4 commits into from

Conversation

vermaete
Copy link
Contributor

@vermaete vermaete commented Mar 1, 2025

Some Kas stuff:

  • fixed a warning about include
  • removed not used iron.yml file
  • git ignore the files and directories created by Kas

br

It is not longer needed to decompress the wic file to be used with
bmaptool.

From the man page fo bmaptool:

  IMAGE may be compressed, in which case bmaptool decompresses it
  on-the-fly.  The compression type is detected by the file extension
  and the following extensions are supported:

      1. ".gz", ".gzip", ".tar.gz" and ".tgz" for files and tar archives
         compressed with "gzip" program

      2. ".bz2", "tar.bz2", ".tbz2", ".tbz", and ".tb2" for files and tar
         archives compressed with "bzip2" program

      3. ".xz", ".tar.xz", ".txz" for files and tar archives compressed
         with "xz" program

      4. ".lzo", "tar.lzo", ".tzo" for files and tar archives compressed
         with "lzo" program

      5. ".lz4", "tar.lz4", ".tlz4" for files and tar archives compressed
         with "lz4" program

      6. ".zst", "tar.zst", ".tzst" for files and tar archives compressed
         with "zstd" program

Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
According to the documentation of kas

  If the path is relative and the configuration file is inside a repository,
  then path is relative to the repositories base directory.

-- See: https://kas.readthedocs.io/en/latest/userguide/project-configuration.html#including-in-tree-configuration-files

Fixed these kind of Kas warnings:
  WARNING  - Falling back to file-relative addressing of local include "yocto/master.yml"
  WARNING  - Update your layer to repo-relative addressing to avoid this warning
  WARNING  - Falling back to file-relative addressing of local include "ros2/jazzy.yml"
  WARNING  - Update your layer to repo-relative addressing to avoid this warning
  WARNING  - Falling back to file-relative addressing of local include "machine/raspberrypi4-64.yml"
  WARNING  - Update your layer to repo-relative addressing to avoid this warning
  WARNING  - Falling back to file-relative addressing of local include "common.yml"
  WARNING  - Update your layer to repo-relative addressing to avoid this warning

Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Ignore the work files and direcories created with kas.

Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
remove the Kas include file for Iron.

Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
@robwoolley
Copy link
Collaborator

Thanks for the fixes. I appreciate you getting rid of those pesky kas warnings as they were a bit of an eyesore.

I am not quite ready to remove iron.yml until I remove the meta-ros2-iron layers across all the branches. As you said, it is unsupported and I already removed the kas configurations. I am not ready to do that yet. I likely will remove it as part of getting ready for Kilted Kaiju.

Regarding the .gitignore changes. The existing file was created for the old "mcf" tool. I don't typically build inside that directory, but I could be convinced to change the documented workflow. I would like to hold off on merging those changes for now until we can better revise the instructions here: https://github.com/ros/meta-ros/blob/build/kas/README.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants