Running an arbitrary emulated binary can help with simple execution and reversing research, but not when it needs to interact with an entire ecosystem of other software.
Emulating an entire system (kernel, base init image, filesystem) is preferred, but much harder as the components must all be cross compiled for the target architecture.
Tools like yocto and buildroot can compose these for you - albiet with significant data and compute time in preparing them.
This story is to research integrating one or both of these tools into a containerised environment to produce cross-compiled system environments on a per-architecture basis, with optional component specifications (e.g. kernel version, libc variant).
Running an arbitrary emulated binary can help with simple execution and reversing research, but not when it needs to interact with an entire ecosystem of other software.
Emulating an entire system (kernel, base init image, filesystem) is preferred, but much harder as the components must all be cross compiled for the target architecture.
Tools like yocto and buildroot can compose these for you - albiet with significant data and compute time in preparing them. This story is to research integrating one or both of these tools into a containerised environment to produce cross-compiled system environments on a per-architecture basis, with optional component specifications (e.g. kernel version, libc variant).