On 8/9/24 11:59 AM, Maciej Barć wrote:
> Hi Sam,
>
> We have a "source" flag so maybe we could either use that or have
> "test-source" BUT we also have FEATURES="installsources" ...so (if I
> understand that feature correctly) we can just run test from
> /usr/src/debug/${CATEGORY}/${PF}
>
> But IMO I'd rather clone the project and run test from the clone.
>
> Of source the drawback of installsources & git cloning is that emerge
> does not run any modifications on the tests nor applies patches to them
> nor buildsystem/testrunner used.installsources is not the same thing at all. That parses ELF files to extract .c / .cpp etc source filenames from debuginfo to save them. This thread is asking about the idea of compiling test programs and installing the test executables so that you can run them later. You absolutely cannot do that with a directory of .c files, for numerous reasons including the fact that it only saves sources for files which get installed anyway, but also because it does not install build system files (meson.build, Makefile, CMakeLists.txt, etc). P.S. See my gnome documentation link, it talks about git cloning too. -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
