search

siemens / kas

Setup tool for bitbake based projects
MIT License
339 stars 145 forks source link

Possible to change KAS_BUILD_DIR within kas yaml config? #116

Open rcross-lc opened 2 months ago

rcross-lc commented 2 months ago

My use case here is that I have a kirkstone.yaml and a scarthgap.yaml and I would like them to have completely separate build directories.

Is there a way to set this up so that I don't need to manage environment variables via another wrapper script?

If not, can this setting be exposed to the yaml config?

jan-kiszka commented 2 months ago

KAS_BUILD_DIR is not really a project setting, it's a local decision. Or why should all users of your configs split the build dirs like you suggest?

But even if we wanted to introduce a configurable default value to the config, that would not work across kas-container. It needs to know this value but has no parser for configs with all their includes and overrides (except for very simplistic top-level evaluations).

rcross-lc commented 2 months ago

I think I understand the problem, I'll investigate why my scarthgap builds can't co-exist with my kirkstone builds and/or change the TMPDIR and cache directories maybe...