Document existing 'make' targets; identify possible new ones

[jkeenan]

As per discussion in #18545 (comment), we should better document our make targets.

Step 1 would be to assemble a list of make targets which contributors and committers currently use. The following come to mind for me (in approximate order of build):

make miniperl
make minitest_prep
make minitest
make
make test_porting
make test_harness

Are there others?

Step 2 would be to prepare a list of make targets we don't currently have but would be nice to have. For example, targets to run tests for just those *.t files in a particular directory tree, whether with miniperl or perl.

[leonerd]

I quite often do make -j4 perl to get just enough of the actual binary, to then do some quick ./perl -Ilib -E... for testing purposes while developing something new

[Corion]

I often use

make -j8 test_prep && HARNESS_OPTIONS=j8 make test_harness

So I also nominate test_prep, in addition to minitest_prep.

There also is test_reonly, but I'm wondering about how we could better formalize speficying a group/set of tests in a more generic way, or if we want that at all.

[Tux]

I was about to nominate test_prep too (or test-prep).
I'd also say regen_headers
And you forgot clean, realclean, veryclean, and distclean

[jkeenan]

I was about to nominate test_prep too (or test-prep).

I can't believe I forgot make test_prep, because I use that all the time.

I'd also say regen_headers
And you forgot clean, realclean, veryclean, and distclean

But there are others which I did not know or never use. I see this as something where we start by documenting the most widely used and going on from there.

[jkeenan]

I've done some preliminary research on this and am going to try to pull together a small group of people to work on this collectively.

[tonycoz]

There also is test_reonly, but I'm wondering about how we could better formalize speficying a group/set of tests in a more generic way, or if we want that at all.

There is:

make test TEST_FILES='op/*.t'

which might not be what you're after.

[demerphq]

You missed test_reonly. Yves

…

On Sun, 21 Aug 2022 at 14:19, James E Keenan ***@***.***> wrote: Closed #18548 <#18548> as completed. — Reply to this email directly, view it on GitHub <#18548 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAZ5RYAJIRQZCUGJPLMA4TV2INFLANCNFSM4XLDNUNA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- perl -Mre=debug -e "/just|another|perl|hacker/"