OrgACRN
/
sof
mirror of https://github.com/thesofproject/sof.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
sof/tools/testbench/CMakeLists.txt

91 lines
2.9 KiB
CMake
Raw Normal View History

cmake: add spdx license identifier Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-06-02 03:33:40 +08:00
# SPDX-License-Identifier: BSD-3-Clause
CMake: require version 3.13 Without CMP0079 we cannot conditionally include libraries against SOF in sub directories without seriously restructuring the project. This is because the old policy requires the link target must be created in the same folder. This does not work well from a configuration standpoint for 3P audio libraries trying to keep their config in src/audio/*. Rather than enable the policy, lets simply upgrade since 3.13 is widely available. With this upgrade we can also remove the two version dependent checks at the top of our scripts. Signed-off-by: Curtis Malainey <cujomalainey@chromium.org>
2021-09-09 05:54:20 +08:00
cmake_minimum_required(VERSION 3.13)
cmake: host: separate testbench build Testbench is user-space application that should just consume SOF library, so it should be moved out from fw buildsystem. Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-04-29 18:16:05 +08:00
project(SOF_TESTBENCH C)
cmake: add testbench host build Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-01-15 17:46:20 +08:00
sof: use RELATIVE_FILE instead of __FILE__ Use RELATIVE_FILE because __FILE__ makes binary output dependent on project location. Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-11-08 01:54:27 +08:00
include(../../scripts/cmake/misc.cmake)
testbench: simplify build to use 1 target Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-04-26 04:11:09 +08:00
add_executable(testbench
testbench.c
cmake: add testbench host build Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-01-15 17:46:20 +08:00
common_test.c
file.c
topology.c
)
sof: use RELATIVE_FILE instead of __FILE__ Use RELATIVE_FILE because __FILE__ makes binary output dependent on project location. Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-11-08 01:54:27 +08:00
sof_append_relative_path_definitions(testbench)
testbench: simplify build to use 1 target Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-04-26 04:11:09 +08:00
target_include_directories(testbench PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/include)
Use '-imacros config.h' instead of explicit #include <config.h> Using -imacros on the compiler command line instead of explicitly including config.h is not just less tedious in the future: - it also makes sure configuration always comes first and is never accidentally missed by an earlier #include - it makes sure all translation units get the (same) configuration - it lets parent projects like Zephyr override the config.h name To test this I ran ./scripts/xtensa-build-all.sh -a -r, compared binaries before and after this change and found no output difference. Full disclosure: this required a few unrelated tricks not submitted here like a .tarball-version file, commenting out __DATE__ and __TIME__ in a few places, running strip-determinism on the .a files because our crosstool-ng reference is not cutting-edge, etc. As Tigerlake is not built by default it required a couple more hacks to compile. Blank lines are left instead of the former #include lines so even debug objects are the same. Only defconfigs were tested. On the other hand, this commit was _not_ performed by a script but by changing the name of the generated file and clicking on and fixing every build failure. This proves that every removed #include was actually required by one or more tested defconfigs and that the added -imacros flag does affect the compilation of all the modified files. There is no #include config.h left: they were all in use in at least one _defconfig. I think comparing all binaries produced by ./scripts/xtensa-build-all.sh -r -a provides extensive enough coverage but note this was tested only with the crosstool-ng toolchain described in the SOF documentation. The obsolete[*] xt-xcc front-end is gcc-based and the newer xt-clang front-end is (surprise) clang-based. clang (copies many gcc options and) does support -imacros so I don't expect any issue with either xt-xcc or xt-clang. In the worst case, I do not expect any compiler front end to _silently_ discard any unknown command line flag nor to ignore a missing or misnamed config.h file. [*] https://github.com/zephyrproject-rtos/zephyr/issues/3165 Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2020-06-12 13:47:37 +08:00
set(sof_source_directory "${PROJECT_SOURCE_DIR}/../..")
set(sof_install_directory "${PROJECT_BINARY_DIR}/sof_ep/install")
set(sof_binary_directory "${PROJECT_BINARY_DIR}/sof_ep/build")
set(config_h ${sof_binary_directory}/library_autoconfig.h)
header: rtos: decouple headers into rtos specific directories. No functional runtime change, but changes to rtos partitioning and the layout of headers . This patch creates RTOS specifc header paths and updates spinlock.h and kernel.h to show the new usage. Other headers will incrementally follow. It reuses the current zephyr topleve directory and creates a new toplevel xtos directory for xtos specific files. Due to the mixing of RTOS, driver and library headers at the top level include directory it was necessary to create rtos specific header directories i.e. src/include/rtos-xtos src/include/rtos-zephyr These RTOS include directories will eventually contain RTOS specific headers whilst common logic and structures will be placed in non RTOS directories. This will also mean "#include <sof/spinlock.h>" will become "#include <rtos/spinlock.h>" and will allow easier visualisation of where and why RTOS headers are being used. This will help to eliminate cross usage of headers between RTOSes. Subsequqnt patches will move more headers and rtos specific wrppaer source files into rtos specific locations. Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
2022-08-19 21:10:56 +08:00
# TODO: testbench should not need RTOS headers: FIX.
if (NOT CONFIG_SOF_ZEPHYR_STRICT_HEADERS)
target_include_directories(testbench PRIVATE
"${PROJECT_SOURCE_DIR}/xtos/include"
)
endif()
Use '-imacros config.h' instead of explicit #include <config.h> Using -imacros on the compiler command line instead of explicitly including config.h is not just less tedious in the future: - it also makes sure configuration always comes first and is never accidentally missed by an earlier #include - it makes sure all translation units get the (same) configuration - it lets parent projects like Zephyr override the config.h name To test this I ran ./scripts/xtensa-build-all.sh -a -r, compared binaries before and after this change and found no output difference. Full disclosure: this required a few unrelated tricks not submitted here like a .tarball-version file, commenting out __DATE__ and __TIME__ in a few places, running strip-determinism on the .a files because our crosstool-ng reference is not cutting-edge, etc. As Tigerlake is not built by default it required a couple more hacks to compile. Blank lines are left instead of the former #include lines so even debug objects are the same. Only defconfigs were tested. On the other hand, this commit was _not_ performed by a script but by changing the name of the generated file and clicking on and fixing every build failure. This proves that every removed #include was actually required by one or more tested defconfigs and that the added -imacros flag does affect the compilation of all the modified files. There is no #include config.h left: they were all in use in at least one _defconfig. I think comparing all binaries produced by ./scripts/xtensa-build-all.sh -r -a provides extensive enough coverage but note this was tested only with the crosstool-ng toolchain described in the SOF documentation. The obsolete[*] xt-xcc front-end is gcc-based and the newer xt-clang front-end is (surprise) clang-based. clang (copies many gcc options and) does support -imacros so I don't expect any issue with either xt-xcc or xt-clang. In the worst case, I do not expect any compiler front end to _silently_ discard any unknown command line flag nor to ignore a missing or misnamed config.h file. [*] https://github.com/zephyrproject-rtos/zephyr/issues/3165 Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2020-06-12 13:47:37 +08:00
target_compile_options(testbench PRIVATE -g -O3 -Wall -Werror -Wl,-EL -Wmissing-prototypes
cmake: allow testbench to build with clang We need clang support for the testbench therefore the following changes are needed remove -ftree-vectorizer-verbose since its deprecated in gcc and not supported in clang remove =3 from -Wimplicit-fallthrough=3 since 3 is the default level anyways Signed-off-by: Curtis Malainey <cujomalainey@chromium.org>
2020-09-24 06:37:10 +08:00
-Wimplicit-fallthrough -DCONFIG_LIBRARY -imacros${config_h})
cmake: host: separate testbench build Testbench is user-space application that should just consume SOF library, so it should be moved out from fw buildsystem. Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-04-29 18:16:05 +08:00
testbench: simplify build to use 1 target Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-04-26 04:11:09 +08:00
target_link_libraries(testbench PRIVATE -ldl -lm)
cmake: add testbench host build Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-01-15 17:46:20 +08:00
install(TARGETS testbench DESTINATION bin)
cmake: host: separate testbench build Testbench is user-space application that should just consume SOF library, so it should be moved out from fw buildsystem. Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-04-29 18:16:05 +08:00
include(ExternalProject)
ExternalProject_Add(sof_ep
DOWNLOAD_COMMAND ""
SOURCE_DIR "${sof_source_directory}"
PREFIX "${PROJECT_BINARY_DIR}/sof_ep"
BINARY_DIR "${sof_binary_directory}"
cmake: merge BUILD_LIBRARY and CONFIG_LIBRARY There is only one valid CONFIG_LIBRARY which can be configured via kconfig Signed-off-by: Adrian Bonislawski <adrian.bonislawski@linux.intel.com>
2020-04-23 21:02:43 +08:00
CMAKE_ARGS -DCONFIG_LIBRARY=ON
cmake: host: separate testbench build Testbench is user-space application that should just consume SOF library, so it should be moved out from fw buildsystem. Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-04-29 18:16:05 +08:00
-DCMAKE_INSTALL_PREFIX=${sof_install_directory}
-DCMAKE_VERBOSE_MAKEFILE=${CMAKE_VERBOSE_MAKEFILE}
cmake: generate the complete .config at configuration time. Add cmake -DINIT_CONFIG= option that can point at any initial file. "make clean" does not delete .config any more. Note reconfiguration does NOT causes recompilation because -imacros hides the generated .h from CMake's dependency scan. This is not a regression, that problems exists since -imacros was introduced. At least it's now possible to "make clean" and rebuild without losing the .config file. Fix for #3617 Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2021-02-05 16:20:16 +08:00
-DINIT_CONFIG=library_defconfig
Use '-imacros config.h' instead of explicit #include <config.h> Using -imacros on the compiler command line instead of explicitly including config.h is not just less tedious in the future: - it also makes sure configuration always comes first and is never accidentally missed by an earlier #include - it makes sure all translation units get the (same) configuration - it lets parent projects like Zephyr override the config.h name To test this I ran ./scripts/xtensa-build-all.sh -a -r, compared binaries before and after this change and found no output difference. Full disclosure: this required a few unrelated tricks not submitted here like a .tarball-version file, commenting out __DATE__ and __TIME__ in a few places, running strip-determinism on the .a files because our crosstool-ng reference is not cutting-edge, etc. As Tigerlake is not built by default it required a couple more hacks to compile. Blank lines are left instead of the former #include lines so even debug objects are the same. Only defconfigs were tested. On the other hand, this commit was _not_ performed by a script but by changing the name of the generated file and clicking on and fixing every build failure. This proves that every removed #include was actually required by one or more tested defconfigs and that the added -imacros flag does affect the compilation of all the modified files. There is no #include config.h left: they were all in use in at least one _defconfig. I think comparing all binaries produced by ./scripts/xtensa-build-all.sh -r -a provides extensive enough coverage but note this was tested only with the crosstool-ng toolchain described in the SOF documentation. The obsolete[*] xt-xcc front-end is gcc-based and the newer xt-clang front-end is (surprise) clang-based. clang (copies many gcc options and) does support -imacros so I don't expect any issue with either xt-xcc or xt-clang. In the worst case, I do not expect any compiler front end to _silently_ discard any unknown command line flag nor to ignore a missing or misnamed config.h file. [*] https://github.com/zephyrproject-rtos/zephyr/issues/3165 Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2020-06-12 13:47:37 +08:00
-DCONFIG_H_PATH=${config_h}
cmake: host: separate testbench build Testbench is user-space application that should just consume SOF library, so it should be moved out from fw buildsystem. Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-04-29 18:16:05 +08:00
BUILD_ALWAYS 1
BUILD_BYPRODUCTS "${sof_install_directory}/lib/libsof.so"
)
add_library(sof_library SHARED IMPORTED)
set_target_properties(sof_library PROPERTIES IMPORTED_LOCATION "${sof_install_directory}/lib/libsof.so")
add_dependencies(sof_library sof_ep)
testbench: Support reuse of topology parser The topology parser in testbench can be re-used for the other applications like the fuzzer. In order to accomplish this, this commit does the following: 1. Separate the topology parser into a separate project (tplg_parser) which implements the callbacks for parsing all the components in topology. 2. Add support for parsing new components such as host pcm, dai and mixer 3. Include the topology parser as an external project in the testbench. Signed-off-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
2019-07-12 12:32:30 +08:00
set(parser_source_directory "${PROJECT_SOURCE_DIR}/../tplg_parser")
set(parser_install_dir "${PROJECT_BINARY_DIR}/sof_parser/install")
#External project for topology parser
ExternalProject_Add(parser_ep
SOURCE_DIR "${parser_source_directory}"
PREFIX "${PROJECT_BINARY_DIR}/sof_parser"
BINARY_DIR "${PROJECT_BINARY_DIR}/sof_parser/build"
testbench: cmake: parser does not use CONFIG_LIBRARY cmake variable Not used by parser cmakefile so delete. Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
2022-08-25 04:05:47 +08:00
CMAKE_ARGS
testbench: Support reuse of topology parser The topology parser in testbench can be re-used for the other applications like the fuzzer. In order to accomplish this, this commit does the following: 1. Separate the topology parser into a separate project (tplg_parser) which implements the callbacks for parsing all the components in topology. 2. Add support for parsing new components such as host pcm, dai and mixer 3. Include the topology parser as an external project in the testbench. Signed-off-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
2019-07-12 12:32:30 +08:00
-DCMAKE_INSTALL_PREFIX=${PROJECT_BINARY_DIR}/sof_parser/install
-DCMAKE_VERBOSE_MAKEFILE=${CMAKE_VERBOSE_MAKEFILE}
BUILD_ALWAYS 1
BUILD_BYPRODUCTS "${parser_install_dir}/lib/libsof_tplg_parser.so"
)
add_library(sof_parser_lib SHARED IMPORTED)
set_target_properties(sof_parser_lib PROPERTIES IMPORTED_LOCATION "${parser_install_dir}/lib/libsof_tplg_parser.so")
add_dependencies(sof_parser_lib parser_ep)
add_dependencies(testbench sof_parser_lib)
cmake: host: separate testbench build Testbench is user-space application that should just consume SOF library, so it should be moved out from fw buildsystem. Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-04-29 18:16:05 +08:00
target_link_libraries(testbench PRIVATE sof_library)
testbench: Support reuse of topology parser The topology parser in testbench can be re-used for the other applications like the fuzzer. In order to accomplish this, this commit does the following: 1. Separate the topology parser into a separate project (tplg_parser) which implements the callbacks for parsing all the components in topology. 2. Add support for parsing new components such as host pcm, dai and mixer 3. Include the topology parser as an external project in the testbench. Signed-off-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
2019-07-12 12:32:30 +08:00
target_link_libraries(testbench PRIVATE sof_parser_lib)
library: testbench: Add LL scheduler emulation Add LL scheduler emulation for testbench pipelines. Each core is implemented as a thread. Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
2021-08-16 23:43:34 +08:00
target_link_libraries(testbench PRIVATE pthread)
cmake: host: separate testbench build Testbench is user-space application that should just consume SOF library, so it should be moved out from fw buildsystem. Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-04-29 18:16:05 +08:00
target_include_directories(testbench PRIVATE ${sof_install_directory}/include)
testbench: Support reuse of topology parser The topology parser in testbench can be re-used for the other applications like the fuzzer. In order to accomplish this, this commit does the following: 1. Separate the topology parser into a separate project (tplg_parser) which implements the callbacks for parsing all the components in topology. 2. Add support for parsing new components such as host pcm, dai and mixer 3. Include the topology parser as an external project in the testbench. Signed-off-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
2019-07-12 12:32:30 +08:00
target_include_directories(testbench PRIVATE ${parser_install_dir}/include)
cmake: host: separate testbench build Testbench is user-space application that should just consume SOF library, so it should be moved out from fw buildsystem. Signed-off-by: Janusz Jankowski <janusz.jankowski@linux.intel.com>
2019-04-29 18:16:05 +08:00
set_target_properties(testbench
PROPERTIES
INSTALL_RPATH "${sof_install_directory}/lib"
INSTALL_RPATH_USE_LINK_PATH TRUE
)