How to use an executable made by a custom_target() as command for test() ? #6567

Activity

1. xclaesse commented on Feb 1, 2020

   

   xclaesse

   on Feb 1, 2020

   Member

   More actions

   I think the short answer is it's not supported. That being said, judging by the code I think something like that could work around it:

   target = custom_target()
   exe = files([target.full_path()])[0]
   test('mytest', exe)

   👍React with 👍1Reacted by lambda-code
2. lambda-code commented on Feb 2, 2020

   

   lambda-code

   on Feb 2, 2020

   Last edited by lambda-code

   Author

   More actions

   @xclaesse yes this trick works fine. It fun to see that the string returned by full_path() doesn't work directly with test(), but with files() yes.
   thanks!

   I wonder if it could be an improvement to let test() works with full_path() directly.
3. xclaesse commented on Feb 3, 2020

   

   xclaesse

   on Feb 3, 2020

   Member

   More actions

   Yes I think it should accept target[0] at least. Would be a nice contribution if you can make a pr ;)
4. eli-schwartz commented on Aug 31, 2021

   

   eli-schwartz

   on Aug 31, 2021

   Member

   More actions

   It doesn't seem to work at all for me, File @target@ does not exist.

   find_program() doesn't work either...

   This seems to be still relevant
5. amcn commented on Mar 23, 2023

   

   amcn

   on Mar 23, 2023

   Contributor

   More actions

   I recently tried to do this assuming that it would work, and after a few searches ended up here. Is there a wide desire for this?

   I looked into seeing what it would take to implement this and to my surprise it's a simple two line change to get the most basic example working (adding build.CustomTarget into the accepted types for Interpretor.func_test and Interpretor.make_test) but that's probably not a good idea as not all custom targets will be executable.

   If the output of custom_target is something that can be executed as a test, then it should probably be an build.Executable, right? Would it make sense to add a new boolean kwarg to custom_target that users can set to true if the output is intended to be executable and which defaults to false?
6. bruchar1

   added 4 commits that reference this issue on Feb 23, 2024

   Allow using CustomTarget as test executable

   ...

   This issue will close once commit c8ce885 is merged into the 'master' branch.

   c8ce885

   Allow using CustomTarget as test executable

   ...

   This issue will close once commit f137891 is merged into the 'master' branch.

   f137891

   Allow using CustomTarget as test executable

   ...

   This issue will close once commit c7b219c is merged into the 'master' branch.

   c7b219c

   Allow using CustomTarget as test executable

   ...

   This issue will close once commit 9f73d01 is merged into the 'master' branch.

   9f73d01
7. dcbaker

   closed this as completedin #12897on Feb 24, 2024
8. dcbaker

   added a commit that references this issue on Feb 24, 2024

   Allow using CustomTarget as test executable

   ...

   This issue will close once commit 11f2e07 is merged into the 'master' branch.

   11f2e07
9. soumyaDghosh

   added a commit that references this issue on Jun 4, 2024

   Allow using CustomTarget as test executable

   ...

   This issue will close once commit baa1d37 is merged into the 'master' branch.

   baa1d37
10. Volker-Weissmann

    added a commit that references this issue on May 1, 2025

    Allow using CustomTarget as test executable

    ...

    This issue will close once commit f51cba2 is merged into the 'master' branch.

    f51cba2
11. bonzini

    added a parent issue on Oct 4, 2025

    • Object consistency #6068