Searched full:uv_run_tests_a (Results 1 – 5 of 5) sorted by relevance
199 $ build/uv_run_tests_a # static library build240 $ build/uv_run_tests_a TEST_NAME247 $ build/uv_run_tests_a TEST_NAME TEST_NAME253 (`build/uv_run_tests_a TEST_NAME TEST_NAME`), tools like gdb and valgrind257 (`build/uv_run_tests_a TEST_NAME`), use these tools in a fork-aware manner.264 $ gdb --args build/uv_run_tests_a TEST_NAME275 …leak-resolution=high --show-reachable=yes --log-file=memcheck-%p.log build/uv_run_tests_a TEST_NAME
643 add_executable(uv_run_tests_a ${uv_test_sources} uv_win_longpath.manifest) target644 target_compile_definitions(uv_run_tests_a PRIVATE ${uv_defines})645 target_compile_options(uv_run_tests_a PRIVATE ${uv_cflags})647 target_link_libraries(uv_run_tests_a uv_a ${uv_test_libraries} -static)649 target_link_libraries(uv_run_tests_a uv_a ${uv_test_libraries})652 COMMAND uv_run_tests_a657 set_target_properties(uv_run_tests_a PROPERTIES LINKER_LANGUAGE CXX)
33 ./build-tsan/uv_run_tests_a41 ./build-asan/uv_run_tests_a
58 ./build/uv_run_tests_a platform_output129 ${{ matrix.config.qemu }} build/uv_run_tests_a
46 build\\Debug\\uv_run_tests_a.exe platform_output