diff options
| author | Amy Huang <akhuang@google.com> | 2025-07-12 14:43:52 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-07-12 14:43:52 -0700 |
| commit | bc2cc8b56e2444339ffa58e83a457d15ae18241d (patch) | |
| tree | cddec8d498adfad6b68f60e51150c7138bdc2a65 /libc | |
| parent | 8afab759d471b60863b8304e39bf6a8b415221dc (diff) | |
Change binary path in libc test cmake file from relative to absolute (#148315)
For some reason cmake usually turns this path into an absolute path, but
sometimes
it doesn't do it and stays as a relative path, which means the command
will fail.
Specify it as an absolute path always so this doesn't happen any more.
Diffstat (limited to 'libc')
| -rw-r--r-- | libc/cmake/modules/LLVMLibCTestRules.cmake | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/libc/cmake/modules/LLVMLibCTestRules.cmake b/libc/cmake/modules/LLVMLibCTestRules.cmake index 1cd09816e223..11937c8c8ab0 100644 --- a/libc/cmake/modules/LLVMLibCTestRules.cmake +++ b/libc/cmake/modules/LLVMLibCTestRules.cmake @@ -327,7 +327,7 @@ function(create_libc_unittest fq_target_name) if(NOT LIBC_UNITTEST_NO_RUN_POSTBUILD) add_custom_target( ${fq_target_name} - COMMAND ${LIBC_UNITTEST_ENV} ${CMAKE_CROSSCOMPILING_EMULATOR} ${fq_build_target_name} + COMMAND ${LIBC_UNITTEST_ENV} ${CMAKE_CROSSCOMPILING_EMULATOR} ${CMAKE_CURRENT_BINARY_DIR}/${fq_build_target_name} COMMENT "Running unit test ${fq_target_name}" DEPENDS ${fq_build_target_name} ) |
