ladybird/Userland/Libraries/LibTest/CMakeLists.txt

serenity_install_sources("Userland/Libraries/LibTest")

set(SOURCES
    TestSuite.cpp
    CrashTest.cpp
)

serenity_lib(LibTest test)

add_library(LibTestMain OBJECT TestMain.cpp)
add_library(JavaScriptTestRunnerMain OBJECT JavaScriptTestRunnerMain.cpp)

if (SERENITYOS)
    add_dependencies(LibTestMain install_libc_headers)
    add_dependencies(JavaScriptTestRunnerMain install_libc_headers)
endif()
LibELF+LibTest: Fix serenity_install_sources() paths Currently we end up with the following: serenity/ AK/ ... Kernel/ ... Libraries/ LibELF/ LibTest/ Userland/ Libraries/ <all other libs> ... 2021-03-14 23:02:53 +00:00			`serenity_install_sources("Userland/Libraries/LibTest")`
AK+Userland: Move AK/TestSuite.h into LibTest and rework Tests' CMake As many macros as possible are moved to Macros.h, while the macros to create a test case are moved to TestCase.h. TestCase is now the only user-facing header for creating a test case. TestSuite and its helpers have moved into a .cpp file. Instead of requiring a TEST_MAIN macro to be instantiated into the test file, a TestMain.cpp file is provided instead that will be linked against each test. This has the side effect that, if we wanted to have test cases split across multiple files, it's as simple as adding them all to the same executable. The test main should be portable to kernel mode as well, so if there's a set of tests that should be run in self-test mode in kernel space, we can accomodate that. A new serenity_test CMake function streamlines adding a new test with arguments for the test source file, subdirectory under /usr/Tests to install the test application and an optional list of libraries to link against the test application. To accomodate future test where the provided TestMain.cpp is not suitable (e.g. test-js), a CUSTOM_MAIN parameter can be passed to the function to not link against the boilerplate main function. 2021-04-25 05:53:23 +00:00
			`set(SOURCES`
			`TestSuite.cpp`
LibTest: Move Crash testing facility from crash.cpp to LibTest 2021-05-07 10:43:41 +00:00			`CrashTest.cpp`
AK+Userland: Move AK/TestSuite.h into LibTest and rework Tests' CMake As many macros as possible are moved to Macros.h, while the macros to create a test case are moved to TestCase.h. TestCase is now the only user-facing header for creating a test case. TestSuite and its helpers have moved into a .cpp file. Instead of requiring a TEST_MAIN macro to be instantiated into the test file, a TestMain.cpp file is provided instead that will be linked against each test. This has the side effect that, if we wanted to have test cases split across multiple files, it's as simple as adding them all to the same executable. The test main should be portable to kernel mode as well, so if there's a set of tests that should be run in self-test mode in kernel space, we can accomodate that. A new serenity_test CMake function streamlines adding a new test with arguments for the test source file, subdirectory under /usr/Tests to install the test application and an optional list of libraries to link against the test application. To accomodate future test where the provided TestMain.cpp is not suitable (e.g. test-js), a CUSTOM_MAIN parameter can be passed to the function to not link against the boilerplate main function. 2021-04-25 05:53:23 +00:00			`)`

			`serenity_lib(LibTest test)`
Meta/LibTest: Build object libraries for test main files By using the power of object libraries and $<TARGET_OBJECTS> we can make sure to only build TestMain.cpp and JavaScriptTestRunnerMain.cpp once. Previously we built these cpp files into object files once for every single test executable. This change reduces the number of total compile jobs in a Serenity target build by around 100. 2021-07-27 06:19:08 +00:00
			`add_library(LibTestMain OBJECT TestMain.cpp)`
			`add_library(JavaScriptTestRunnerMain OBJECT JavaScriptTestRunnerMain.cpp)`
Everywhere: Resolve conflicts with LibC and libc++ Since https://reviews.llvm.org/D131441, libc++ must be included before LibC. As clang includes libc++ as one of the system includes, LibC must be included after those, and the only correct way to do that is to install LibC's headers into the sysroot. Targets that don't link with LibC yet require its headers for one reason or another must add install_libc_headers as a dependency to ensure that the correct headers have been (re)installed into the sysroot. LibC/stddef.h has been dropped since the built-in stddef.h receives a higher include priority. In addition, string.h and wchar.h must define __CORRECT_ISO_CPP_STRING_H_PROTO and _LIBCPP_WCHAR_H_HAS_CONST_OVERLOADS respectively in order to tell libc++ to not try to define methods implemented by LibC. 2023-04-28 18:55:59 +00:00
			`if (SERENITYOS)`
			`add_dependencies(LibTestMain install_libc_headers)`
			`add_dependencies(JavaScriptTestRunnerMain install_libc_headers)`
			`endif()`