Re: compile EPICS without examples and tests

[Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov>]

On 6/8/22 10:35, Andrew Johnson via Tech-talk wrote:
> Hi,
>
> On 6/8/22 12:07 PM, William Kirstaedter via Tech-talk wrote:
> > is that possible?
> >
> > it would reduce the compile time on raspberry pis quite a lot, I think.
You have run these tests at least once right?

I can understand not wanting to keep re-building them,
but I would recommend running the tests for each new
(to you) Base version.


> There is no mechanism available to do that in the EPICS build system at the moment, but it might not be too hard to add if that's a project which interests you and you have an understand of GNU Makefiles (or you can persuade someone else to work on it who does).
>
> I would start by adding a switch to configure/CONFIG_SITE which prevents the $(TESTPRODTARGETS)  and $(TESTSCRIPTS) variables being expanded as dependencies of the build: rule in configure/RULES_BUILD, and also excluding the $(TESTLIBNAME), $(TESTSHRLIBNAME) and $(TESTDLLSTUB_LIBNAME) from being added to LIBTARGETS a few lines above that. That switch should also prevent RUNTESTS_ENABLED from being set a few lines above that. There should be no need to disable most of the other settings that use variable names beginning with or containing the word TEST, but there might be some other things that need doing for it to work properly.
As I understand Make variables.  Doesn't a definition from the command line prevent later redefinition?

so:

> make TESTPROD= TESTSCRIPTS=
prevents various test/Makefile from appending test executables and the associated scripts.


> Let me know if you do plan/start to work on this, I'm responsible for the build system and should be able to help with specific problems that could arise.
>
> - Andrew