[jajanusz]

Please merge it only after someone who is actively working with tools approves it.
It should be OK I tried to directly translate rules, but I'm not sure if I didn't miss some important tools that you use every day.

How to build & install:

cmake -Bbuild .
cd build
make
make install

[jajanusz]

@xiulipan

+ ./scripts/docker-run.sh make -C tools/ tests -j4
make: *** No rule to make target 'Makefile.am', needed by 'Makefile.in'.  Stop.

Please change that (in jenkins ci), because it relies on internals of makefiles that was deleted.
It's better to use what is documented and I also support that -> make tests from tools directory, or build-tools.sh -t

[lgirdwood]

We will also need to include changes to the sof-target -install script here to update topology & tools build dir.

Btw, how do we create a tarball release of all source files ?

[lgirdwood]

What's the prefix for destination ? I'm assuming it can be set somewhere.

[jajanusz]

Similar to --prefix from autotools:
https://cmake.org/cmake/help/latest/variable/CMAKE_INSTALL_PREFIX.html

[lgirdwood]

Would it be better to name this build_tools ? or build/tools. Where is the "host build" target built ?

[jajanusz]

By 'host' i guess you mean testbench that was added in FW buildsystem, because it was there previously as --enable-library(?) option. It was direct port of that, but I plan to separate testbench/fw builds.

[jajanusz]

Also I can change build dir name to build_tools, however there is nothing else build from this project that's why I named it just build (for fw you have various builds for platfroms/ut/host so it's differnt story there).

[jajanusz]

Btw, how do we create a tarball release of all source files ?

It's missing functionality, can you create issue and write there what target name you want, for example make dist/make tarball. It's going to be simple, git archive + .tarball-version

[jajanusz]

@lgirdwood Changed as suggested.
I also renamed sof-target-intsall to sof-target-install (had typo), I hope CI doesn't run this script with old wrong name

[lgirdwood]

Btw, how do we create a tarball release of all source files ?

It's missing functionality, can you create issue and write there what target name you want, for example make dist/make tarball. It's going to be simple, git archive + .tarball-version

Done. It's #954

[lgirdwood]

I'm working on topology atm so will get a chance to test tomorrow.

[xiulipan]

@jajanusz
Update the test scripts of sof-ci. Sorry about that old workaround for test topology build.
Please rebase the PR and re-trigger all CIs.

[jajanusz]

@xiulipan @lgirdwood
updated

[lgirdwood]

Is ci failure due to the ci script using autotools ?

[jajanusz]

Is ci failure due to the ci script using autotools ?

No, just don't believe QB tests done in the weekend (after stress tests) because it will fail every time with python tests and then @zrombel has to manually rerun them... I don't know how/when they gonna fix it ;)

[jajanusz]

@ranj063 @lgirdwood
Is it good to merge?
@xiulipan
Why there are no jenkins CIs?

[lgirdwood]

@jajanusz I'm good if you are confirming CI code scan is OK now ?

[jajanusz]

@lgirdwood I did push for jenkins CI, it works, idk tho if QB build will work this time because IT servers are up and down randomly but it was ok before i rerun it

[jajanusz]

@jajanusz I'm good if you are confirming CI code scan is OK now ?

It's ok now