Bug 40072: Move capture_exec to a separate module
1 unresolved thread
1 unresolved thread
Because the RBM and RBM::DefaultConfig modules have circular dependencies,
exporting functions from RBM to RBM::DefaultConfig doesn't work, which
means that part of the changes for #40068 (closed) didn't work. We could fix
that by using RBM::capture_exec
instead of capture_exec
. An other
solution is to make a separate module for capture_exec
. Since the RBM
modules is becoming big, I think it's a good idea to move independent
parts to a separate modules.
/closes #40072 (closed)
Tested while testing the changes for #40071 (closed), doing an android build.
Merge request reports
Activity
requested review from @richard
assigned to @boklm
mentioned in merge request !58 (merged)
Please register or sign in to reply