CMake-generated paths are absolute about camkes-vm-examples-manifest HOT 3 CLOSED

It's generally expected that ../init-build.sh is called from the docker container. It invokes CMake for the first time and CMake detects which toolchains and flags to use from the host environment which needs to be the same as the environment that Ninja is called from.
What reasons do you have for needing to run ../init-build.sh from outside of the docker?

from camkes-vm-examples-manifest.

Do you have an output of which parts of the build script CMake is complaining about? It could be something easy to change to use relative paths anyway. I expect that any part of the build that references CMAKE_SOURCE_DIR or CMAKE_BINARY_DIR will use an absolute path and not work across different directory mounts.

from camkes-vm-examples-manifest.

It's generally expected that ../init-build.sh is called from the docker container.

Ah in that case I'd say that this is a user error :) It does make sense to run them from the same environment, for me it was simply a matter of convenience since my shell completion has the ../init-build.sh invocation saved.

We can probably close this issue in that case.

from camkes-vm-examples-manifest.