testbench: dont build testbench, tools and topologies in the source directory
Currently all topologies, testbench and some tools are built within the FW source directory unlike FW which has separate binary destination directories outside of the main FW source directory.
This series moves all tools, testbench and topologies binaries to outside the source directory to the parent SOF "workspace" directory alongside the FW build output directories.
I expect this to break CI if we have hard coded assumptions of where to find certain binaries. @singalsu pls take a look.
This depends on https://github.com/thesofproject/sof/pull/9870 so DNM as for now.
Changes for V2:
- Check for
SOF_WORKSPACEenvironment for non default installs. - Added @singalsu patch.
depends on https://github.com/thesofproject/sof/pull/9870
@jsarha fyi - was meaning this one.
Rebased now that #9870 is merged
Needs Jenkins update to merge.
Yeah - hopefully the last one. @cgturner1 pls see jenkins build i.e. we no longer build tools in the src directory.
/usr/bin/mkdir -p -m 0755 /home/cwd_user/work/sof/tools/var/lib/alsa
make[3]: Leaving directory '/home/cwd_user/work/sof/alsa-utils'
make[2]: Leaving directory '/home/cwd_user/work/sof/alsa-utils'
make[1]: Leaving directory '/home/cwd_user/work/sof/alsa-utils'
Build and installation complete for /home/cwd_user/work/sof/alsa-utils
All repositories processed.
mkdir: cannot create directory '/home/sof/work/sof.git/../build-tools-tplg': Permission denied
ok will need to take a look...a lot of the issues stem from the user settings (in scripts/sudo-cwd.sh) being done in the docker which seem to be from the way it mounts uses the local volumes as a workspace
and it sems to restrict the user "cwd" from creating directories in certain places ...ideally this docker should run as the sof user and we would be fine..i'll need to figure out the change to get this to cooperate at least to get the mkdir to work.
will run some tests and update when i get this updated