Doğan Ulus

Thank you @brkay54. I will wait for your report. Looks very useful.

> LGTM, but we need to change the documentation of [building containers from scratch](https://github.com/autowarefoundation/autoware-documentation/blob/cefcc1ac46a36ad5be0d8ea7c59d2d0b247062fd/docs/installation/autoware/docker-installation.md?plain=1#L118) section because the user would need to do`vcs import` before building the containers after merging this...

Hi @mitsudome-r, I have shared a snippet of the solution here. It might be missed in a merged PR: https://github.com/autowarefoundation/autoware/pull/4712#issuecomment-2121881833 Regarding this comment: > Therefore, there is a trade-off between...

> if you can create another branch with your solution then we can test out and see if excluding vcs import really needed ? Please describe how you see a...

There are several use case where a more grained `absl` build is desired. I may go a separate `absl` build but then I have to track the version used by...

Thank you, @simonsag96, for your detailed answer. I was looking to avoid ROS and its tooling completely.

I was looking to evaluate if we could use your work alongside a simulator like [Esmini](https://github.com/esmini/esmini/). I believe your equations could be used in different ways there. A standalone library...

One of our goals is to use `esmini` in headless mode inside containers, so we are very much interested in cloud-native configuration styles. [Environment variables](https://12factor.net/config), [configuration dropins/overrides](https://uapi-group.org/specifications/specs/configuration_files_specification/), and default file...

I think an environment variable called `ESMINI_CONFIG_PATH` would be very useful. Still, it can be set to a relative path as the default for the application. The shared library case...

Sounds good. It is easy to add environment variables later if desired. It is possible in YAML to group `esmini` options hierarchically. Do you think this is a good idea?...