From 14c82dbdf6c37f4926c6eb7a35d5c0ca37a5272a Mon Sep 17 00:00:00 2001 From: daylinmorgan Date: Thu, 19 Jan 2023 19:45:04 +0000 Subject: [PATCH] deploy: f27b5fc7e69125514aaf61e7a1fb813a40667eee --- index.html | 8 ++++---- search/search_index.json | 2 +- sitemap.xml.gz | Bin 250 -> 250 bytes 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/index.html b/index.html index 7dd6b92..9820d5d 100644 --- a/index.html +++ b/index.html @@ -587,17 +587,17 @@ to add some QOL improvements for your users and fellow maintainers.

Depends on GNU Make, obviously and Python >=3.7, and bash (or zsh).

Wait python?!?!, I'm not pip installing some package just to parse my makefile. -I agree, all you need is one file .task.mk. +I agree, all you need is one file .task.mk. You can automagically include it with just two additional lines to your Makefile (and probably one to your .gitignore) and your good to go.

Setup

You can include this as an optional dependency on your project by adding the below lines to the end of your Makefile. If someone tries to invoke make help it will download .task.mk for them.

-include .task.mk
-$(if $(filter help,$(MAKECMDGOALS)),$(if $(wildcard .task.mk),,.task.mk: ; curl -fsSL https://raw.githubusercontent.com/daylinmorgan/task.mk/v22.9.28/task.mk -o .task.mk))
+$(if $(filter help,$(MAKECMDGOALS)),$(if $(wildcard .task.mk),,.task.mk: ; curl -fsSL https://raw.githubusercontent.com/daylinmorgan/task.mk/v23.1.1/task.mk -o .task.mk))

You might also consider making it a consistently downloaded dependency if you plan to use any of it's advanced feature set, by dropping the $(MAKECMDGOALS) check.

-include .task.mk
-$(if $(wildcard .task.mk),,.task.mk: ; curl -fsSL https://raw.githubusercontent.com/daylinmorgan/task.mk/v22.9.28/task.mk -o .task.mk)
+$(if $(wildcard .task.mk),,.task.mk: ; curl -fsSL https://raw.githubusercontent.com/daylinmorgan/task.mk/v23.1.1/task.mk -o .task.mk)

Alternatively, you can use the builtin rule _update-task.mk to update to the latest development version.

See Usage to get started running all your tasks. @@ -634,7 +634,7 @@ But like just it's a tool people don't usually already have and it' Last update: - September 28, 2022 + January 19, 2023
Created: diff --git a/search/search_index.json b/search/search_index.json index 44eb142..c88ce3c 100644 --- a/search/search_index.json +++ b/search/search_index.json @@ -1 +1 @@ -{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Home","text":"task.mk

the task runner for GNU Make you've been missing

GNU make is an excellent build tool and the task runner we love to hate, but can't escape. So let's improve the UX to make it the best task runner it can be.

Task.mk, is a standalone Makefile you can deploy alongside your own to add some QOL improvements for your users and fellow maintainers.

Current Features:

Depends on GNU Make, obviously and Python >=3.7, and bash (or zsh).

Wait python?!?!, I'm not pip installing some package just to parse my makefile. I agree, all you need is one file .task.mk. You can automagically include it with just two additional lines to your Makefile (and probably one to your .gitignore) and your good to go.

"},{"location":"#setup","title":"Setup","text":"

You can include this as an optional dependency on your project by adding the below lines to the end of your Makefile. If someone tries to invoke make help it will download .task.mk for them.

-include .task.mk\n$(if $(filter help,$(MAKECMDGOALS)),$(if $(wildcard .task.mk),,.task.mk: ; curl -fsSL https://raw.githubusercontent.com/daylinmorgan/task.mk/v22.9.28/task.mk -o .task.mk))\n

You might also consider making it a consistently downloaded dependency if you plan to use any of it's advanced feature set, by dropping the $(MAKECMDGOALS) check.

-include .task.mk\n$(if $(wildcard .task.mk),,.task.mk: ; curl -fsSL https://raw.githubusercontent.com/daylinmorgan/task.mk/v22.9.28/task.mk -o .task.mk)\n

Alternatively, you can use the builtin rule _update-task.mk to update to the latest development version.

See Usage to get started running all your tasks. See Examples for more use cases.

"},{"location":"#zsh-completions-for-gnu-make","title":"Zsh Completions for GNU Make","text":"

If you use GNU Make with zsh you may want to add the following line to your rc file to allow make to handle the autocomplete.

zstyle ':completion::complete:make:*:targets' call-command true\n
"},{"location":"#why-make","title":"Why Make?","text":"

There are lot of GNU Make alternatives but none have near the same level of ubiquity. This project attaches to make some of the native features of just, a command runner.

Just is a great task runner, but it suffers two problems, users probably don't have it installed already, and there is no way to define file specific recipes. Most of my Makefile's are comprised primarily of handy .PHONY recipes, but I always end up with a few file specific recipes.

Another interesting project I've evaluated for these purposes is go-task/task. Task has many of the features of GNU Make and some novel features of it's own. But like just it's a tool people don't usually already have and it's configured using a yaml file. Yaml files can be finicky to work with and and it uses a golang based shell runtime, not your native shell, which might lead to unexpected behavior.

"},{"location":"#simpler-alternative","title":"Simpler Alternative","text":"

But I just want a basic help output, surely I don't need python for this... you would be right. Task.mk replaces my old make help recipe boilerplate which may better serve you (so long as you have sed/awk).

## h, help | show this help\n.PHONY: help h\nhelp h: Makefile\n@awk -v fill=$(shell sed -n 's/^## \\(.*\\) | .*/\\1/p' $< | wc -L)\\\n'match($$0,/^## (.*) \\|/,name) && match($$0,/\\| (.*)$$/,help)\\\n        {printf \"\\033[1;93m%*s\\033[0m | \\033[30m%s\\033[0m\\n\",\\\n        fill,name[1],help[1];} match($$0,/^### (.*)/,str) \\\n        {printf \"%*s   \\033[30m%s\\033[0m\\n\",fill,\" \",str[1];}' $<\n
"},{"location":"usage/","title":"Usage","text":"

Task.mk will add access to a recipe help (also aliased to h). In order to use make help to you will need to add some custom comments to your Makefile.

Deliberately, I don't get names from recipes themselves. This not only greatly simplifies the parsing but add's some opportunity to customize the output. Such as to document wildcard or redundant recipes.

You can place these anywhere, but I recommend adding these notes directly above their relevant recipes. The format is ## <recipe> | <msg>

## build | build the project\n.PHONY: build\nbuild:\n...\n

Now when you invoke make help it will parse these and generate your help output.

In addition to a generic help output you can expose some configuration settings with make vars. To do so define the variables you'd like to print with PRINT_VARS := VAR1 VAR2 VAR3.

In addition to the help and vars recipes you can use a custom make function to format your text for fancier output. For this there are two options depending on your needs tprint or tprint-sh. (tprint-sh is for use within a multiline sub-shell that has already been silenced, see the version-check rule of this project's Makefile for an example.)

To use tprint you call it with the builtin make call function. It accepts only one argument: an unquoted f-string literal. All strings passed to tprint have access to an object ansi or a for simplicity. This stores ANSI escape codes which can be used to style your text.

## build | compile the source\n.PHONY: build\nbuild:\n$(call tprint,{a.cyan}Build Starting{a.end})\n...\n  $(call tprint,{a.green}Build Finished{a.end})\n
See this projects make info for more examples of tprint.

To see the available colors and formatting(bold,italic,etc.) use the hidden recipe make _print-ansi.

Note: Any help commands starting with an underscore will be ignored. To view hidden tasks (or recipes in GNU Make land) you can use make _help.

In addition, you can use custom colors using the builtin ansi.custom or (a.custom) method. It has two optional arguments fg and bg. Which can be used to specify either an 8-bit color from the 256 colors. Or a tuple/list to define an RBG 24-bit color, for instance a.custom(fg=(5,10,255)). See this project's make info for an example.

"},{"location":"usage/#configuration","title":"Configuration","text":"

You can quickly customize some of the default behavior of task.mk by overriding the below variables prior to the -include .task.mk.

# ---- [config] ---- #\nHEADER_STYLE ?= b_cyan\nACCENT_STYLE ?= b_yellow\nPARAMS_STYLE ?= $(ACCENT_STYLE)\nGOAL_STYLE ?= $(ACCENT_STYLE)\nMSG_STYLE ?= faint\nDIVIDER_STYLE ?= default\nDIVIDER ?= \u2500\nHELP_SEP ?= \u2502\n# python f-string literals\nEPILOG ?=\nUSAGE ?={ansi.$(HEADER_STYLE)}usage{ansi.end}:\\n  make <recipe>\\n\nINHERIT_SHELL ?=\n

To use a custom color for one of the predefined configuration variables specify only the custom method.

HEADER_STYLE = custom(fg=171,bg=227)\n

NOTE: HELP_SEP does not change the argument definitions syntax only the format of make help.

"},{"location":"usage/#advanced-usage-embedded-python-scripts","title":"Advanced Usage: Embedded Python Scripts","text":"

You can take advantage of the builtin python script runner and write multi-line python scripts of your own. This is a simple example but a few lines of python in your Makefile may be easier than balancing sub-shells and strung together awk commands.

When make expands the function it will take the parameters passed to py and expand them. $(1) is the variable name and $(2) in this case is the implicit pattern from the rule. Pay attention to quotes. If you need to debug your python script, use TASKMK_DEBUG=1 when you run make and it will first print the script that will be piped to python.

define list_files_py\nfrom pathlib import Path\nprint(\"files in $(2)\")\nprint([f.name for f in (Path(\"$(2)\").iterdir())])\nendef\n## list-% | use pathlib.Path to list files\nlist-%:\n$(call py,list_files_py,$*)\n

For what it's worth there is also a predefined function for bash (named tbash) as well should you need to accomplish something similar of more easily embedding your bash script rather than having to escape every line with a backslash.

define bash_script\nfiglet task.mk 2>/dev/null || echo 'no figlet :('\necho \"This is from bash\"\ncat /etc/hostname\nprintf \"%s\\n\" \"$(2)\"\nendef\n.PHONY: test-bash\ntest-bash:\n$(call tbash,bash_script,test bash multiline)\n
"},{"location":"examples/","title":"Examples","text":"Confirm

Perform a basic confirmation test with the user and exit with error code 1 if input is N/n.

Embedded Scripts

Use the builtin functions to write multi-line python/bash scripts directly in your Makefile

Recipe Help

Display the target, docstring and recipe for a given target then exit.

"},{"location":"examples/check/","title":"Check","text":"check.mk
## check | get user confirmation or exit\n.PHONY: check\ncheck:\n$(call tconfirm,Would you like to proceed?)\n@echo \"you said yes!\"\ndefine USAGE\n{a.$(HEADER_STYLE)}usage:{a.end}\n    make <recipe>\n\ninteractivity w/ task.mk\\n\nendef\n.DEFAULT_GOAL = help\ninclude $(shell git rev-parse --show-toplevel)/task.mk\n
"},{"location":"examples/embedded/","title":"Embedded","text":"embedded.mk
### examples of task.mk features | args: --divider --align center --msg-style b_red\ndefine list_files_py\nfrom pathlib import Path\nprint(\"files in $(2)\")\nprint([f.name for f in (Path(\"$(2)\").iterdir())])\nendef\n## list-% | use pathlib.Path to list files\n### name the directory in rule (make list-src) | args: --align sep\nlist-%:\n$(call py,list_files_py,$*)\n# dollar signs will always be a problem\ndefine bash_script\necho \"Is the process running bash? We can check with ps\"\nps -o args= -p $$$$ | grep -E -m 1 -o '\\w{0,5}sh'\nif [ -x \"$(command -v figlet)\" ]; then\necho 'no figlet :('\nelse\necho \"What text to figlet? \"\nread name\n    figlet $$name\nfi\necho \"the argument below as given in the makefile itself\"\necho \"it's expanded before the script is passed to bash\"\nprintf \"%s\\n\" \"$(2)\"\nendef\n## embedded-bash | bash script with pipes and make input\n.PHONY: embedded-bash\nembedded-bash:\n$(call tbash,bash_script,bash multiline is probably working)\ndefine USAGE\n{a.$(HEADER_STYLE)}usage:{a.end}\n    make <recipe>\n\nexamples of embedded scripts in `{a.magenta}Makefile{a.end}`\nendef\n.DEFAULT_GOAL = help\ninclude $(shell git rev-parse --show-toplevel)/task.mk\n
"},{"location":"examples/recipe-help/","title":"Recipe Help","text":"recipe-help.mk
## deps-only | a task/target with dependencies\n.PHONY: deps-only\ndeps-only: foo\n## foo | a dummy rule that depends on the local files\n.PHONY: foo\nfoo: $(wildcard *)\n@echo 'this is a dummy rule'\n# bar but no docstring\n.PHONY: bar\nbar:\n@echo 'some rule with no help string'\ndefine USAGE\n{a.header}usage:{a.end}\n    make <recipe>\n    make help <recipe>\n\nendef\n.DEFAULT_GOAL = help\ninclude $(shell git rev-parse --show-toplevel)/task.mk\n
"}]} \ No newline at end of file +{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Home","text":"task.mk

the task runner for GNU Make you've been missing

GNU make is an excellent build tool and the task runner we love to hate, but can't escape. So let's improve the UX to make it the best task runner it can be.

Task.mk, is a standalone Makefile you can deploy alongside your own to add some QOL improvements for your users and fellow maintainers.

Current Features:

Depends on GNU Make, obviously and Python >=3.7, and bash (or zsh).

Wait python?!?!, I'm not pip installing some package just to parse my makefile. I agree, all you need is one file .task.mk. You can automagically include it with just two additional lines to your Makefile (and probably one to your .gitignore) and your good to go.

"},{"location":"#setup","title":"Setup","text":"

You can include this as an optional dependency on your project by adding the below lines to the end of your Makefile. If someone tries to invoke make help it will download .task.mk for them.

-include .task.mk\n$(if $(filter help,$(MAKECMDGOALS)),$(if $(wildcard .task.mk),,.task.mk: ; curl -fsSL https://raw.githubusercontent.com/daylinmorgan/task.mk/v23.1.1/task.mk -o .task.mk))\n

You might also consider making it a consistently downloaded dependency if you plan to use any of it's advanced feature set, by dropping the $(MAKECMDGOALS) check.

-include .task.mk\n$(if $(wildcard .task.mk),,.task.mk: ; curl -fsSL https://raw.githubusercontent.com/daylinmorgan/task.mk/v23.1.1/task.mk -o .task.mk)\n

Alternatively, you can use the builtin rule _update-task.mk to update to the latest development version.

See Usage to get started running all your tasks. See Examples for more use cases.

"},{"location":"#zsh-completions-for-gnu-make","title":"Zsh Completions for GNU Make","text":"

If you use GNU Make with zsh you may want to add the following line to your rc file to allow make to handle the autocomplete.

zstyle ':completion::complete:make:*:targets' call-command true\n
"},{"location":"#why-make","title":"Why Make?","text":"

There are lot of GNU Make alternatives but none have near the same level of ubiquity. This project attaches to make some of the native features of just, a command runner.

Just is a great task runner, but it suffers two problems, users probably don't have it installed already, and there is no way to define file specific recipes. Most of my Makefile's are comprised primarily of handy .PHONY recipes, but I always end up with a few file specific recipes.

Another interesting project I've evaluated for these purposes is go-task/task. Task has many of the features of GNU Make and some novel features of it's own. But like just it's a tool people don't usually already have and it's configured using a yaml file. Yaml files can be finicky to work with and and it uses a golang based shell runtime, not your native shell, which might lead to unexpected behavior.

"},{"location":"#simpler-alternative","title":"Simpler Alternative","text":"

But I just want a basic help output, surely I don't need python for this... you would be right. Task.mk replaces my old make help recipe boilerplate which may better serve you (so long as you have sed/awk).

## h, help | show this help\n.PHONY: help h\nhelp h: Makefile\n@awk -v fill=$(shell sed -n 's/^## \\(.*\\) | .*/\\1/p' $< | wc -L)\\\n'match($$0,/^## (.*) \\|/,name) && match($$0,/\\| (.*)$$/,help)\\\n        {printf \"\\033[1;93m%*s\\033[0m | \\033[30m%s\\033[0m\\n\",\\\n        fill,name[1],help[1];} match($$0,/^### (.*)/,str) \\\n        {printf \"%*s   \\033[30m%s\\033[0m\\n\",fill,\" \",str[1];}' $<\n
"},{"location":"usage/","title":"Usage","text":"

Task.mk will add access to a recipe help (also aliased to h). In order to use make help to you will need to add some custom comments to your Makefile.

Deliberately, I don't get names from recipes themselves. This not only greatly simplifies the parsing but add's some opportunity to customize the output. Such as to document wildcard or redundant recipes.

You can place these anywhere, but I recommend adding these notes directly above their relevant recipes. The format is ## <recipe> | <msg>

## build | build the project\n.PHONY: build\nbuild:\n...\n

Now when you invoke make help it will parse these and generate your help output.

In addition to a generic help output you can expose some configuration settings with make vars. To do so define the variables you'd like to print with PRINT_VARS := VAR1 VAR2 VAR3.

In addition to the help and vars recipes you can use a custom make function to format your text for fancier output. For this there are two options depending on your needs tprint or tprint-sh. (tprint-sh is for use within a multiline sub-shell that has already been silenced, see the version-check rule of this project's Makefile for an example.)

To use tprint you call it with the builtin make call function. It accepts only one argument: an unquoted f-string literal. All strings passed to tprint have access to an object ansi or a for simplicity. This stores ANSI escape codes which can be used to style your text.

## build | compile the source\n.PHONY: build\nbuild:\n$(call tprint,{a.cyan}Build Starting{a.end})\n...\n  $(call tprint,{a.green}Build Finished{a.end})\n
See this projects make info for more examples of tprint.

To see the available colors and formatting(bold,italic,etc.) use the hidden recipe make _print-ansi.

Note: Any help commands starting with an underscore will be ignored. To view hidden tasks (or recipes in GNU Make land) you can use make _help.

In addition, you can use custom colors using the builtin ansi.custom or (a.custom) method. It has two optional arguments fg and bg. Which can be used to specify either an 8-bit color from the 256 colors. Or a tuple/list to define an RBG 24-bit color, for instance a.custom(fg=(5,10,255)). See this project's make info for an example.

"},{"location":"usage/#configuration","title":"Configuration","text":"

You can quickly customize some of the default behavior of task.mk by overriding the below variables prior to the -include .task.mk.

# ---- [config] ---- #\nHEADER_STYLE ?= b_cyan\nACCENT_STYLE ?= b_yellow\nPARAMS_STYLE ?= $(ACCENT_STYLE)\nGOAL_STYLE ?= $(ACCENT_STYLE)\nMSG_STYLE ?= faint\nDIVIDER_STYLE ?= default\nDIVIDER ?= \u2500\nHELP_SEP ?= \u2502\n# python f-string literals\nEPILOG ?=\nUSAGE ?={ansi.$(HEADER_STYLE)}usage{ansi.end}:\\n  make <recipe>\\n\nINHERIT_SHELL ?=\n

To use a custom color for one of the predefined configuration variables specify only the custom method.

HEADER_STYLE = custom(fg=171,bg=227)\n

NOTE: HELP_SEP does not change the argument definitions syntax only the format of make help.

"},{"location":"usage/#advanced-usage-embedded-python-scripts","title":"Advanced Usage: Embedded Python Scripts","text":"

You can take advantage of the builtin python script runner and write multi-line python scripts of your own. This is a simple example but a few lines of python in your Makefile may be easier than balancing sub-shells and strung together awk commands.

When make expands the function it will take the parameters passed to py and expand them. $(1) is the variable name and $(2) in this case is the implicit pattern from the rule. Pay attention to quotes. If you need to debug your python script, use TASKMK_DEBUG=1 when you run make and it will first print the script that will be piped to python.

define list_files_py\nfrom pathlib import Path\nprint(\"files in $(2)\")\nprint([f.name for f in (Path(\"$(2)\").iterdir())])\nendef\n## list-% | use pathlib.Path to list files\nlist-%:\n$(call py,list_files_py,$*)\n

For what it's worth there is also a predefined function for bash (named tbash) as well should you need to accomplish something similar of more easily embedding your bash script rather than having to escape every line with a backslash.

define bash_script\nfiglet task.mk 2>/dev/null || echo 'no figlet :('\necho \"This is from bash\"\ncat /etc/hostname\nprintf \"%s\\n\" \"$(2)\"\nendef\n.PHONY: test-bash\ntest-bash:\n$(call tbash,bash_script,test bash multiline)\n
"},{"location":"examples/","title":"Examples","text":"Confirm

Perform a basic confirmation test with the user and exit with error code 1 if input is N/n.

Embedded Scripts

Use the builtin functions to write multi-line python/bash scripts directly in your Makefile

Recipe Help

Display the target, docstring and recipe for a given target then exit.

"},{"location":"examples/check/","title":"Check","text":"check.mk
## check | get user confirmation or exit\n.PHONY: check\ncheck:\n$(call tconfirm,Would you like to proceed?)\n@echo \"you said yes!\"\ndefine USAGE\n{a.$(HEADER_STYLE)}usage:{a.end}\n    make <recipe>\n\ninteractivity w/ task.mk\\n\nendef\n.DEFAULT_GOAL = help\ninclude $(shell git rev-parse --show-toplevel)/task.mk\n
"},{"location":"examples/embedded/","title":"Embedded","text":"embedded.mk
### examples of task.mk features | args: --divider --align center --msg-style b_red\ndefine list_files_py\nfrom pathlib import Path\nprint(\"files in $(2)\")\nprint([f.name for f in (Path(\"$(2)\").iterdir())])\nendef\n## list-% | use pathlib.Path to list files\n### name the directory in rule (make list-src) | args: --align sep\nlist-%:\n$(call py,list_files_py,$*)\n# dollar signs will always be a problem\ndefine bash_script\necho \"Is the process running bash? We can check with ps\"\nps -o args= -p $$$$ | grep -E -m 1 -o '\\w{0,5}sh'\nif [ -x \"$(command -v figlet)\" ]; then\necho 'no figlet :('\nelse\necho \"What text to figlet? \"\nread name\n    figlet $$name\nfi\necho \"the argument below as given in the makefile itself\"\necho \"it's expanded before the script is passed to bash\"\nprintf \"%s\\n\" \"$(2)\"\nendef\n## embedded-bash | bash script with pipes and make input\n.PHONY: embedded-bash\nembedded-bash:\n$(call tbash,bash_script,bash multiline is probably working)\ndefine USAGE\n{a.$(HEADER_STYLE)}usage:{a.end}\n    make <recipe>\n\nexamples of embedded scripts in `{a.magenta}Makefile{a.end}`\nendef\n.DEFAULT_GOAL = help\ninclude $(shell git rev-parse --show-toplevel)/task.mk\n
"},{"location":"examples/recipe-help/","title":"Recipe Help","text":"recipe-help.mk
## deps-only | a task/target with dependencies\n.PHONY: deps-only\ndeps-only: foo\n## foo | a dummy rule that depends on the local files\n.PHONY: foo\nfoo: $(wildcard *)\n@echo 'this is a dummy rule'\n# bar but no docstring\n.PHONY: bar\nbar:\n@echo 'some rule with no help string'\ndefine USAGE\n{a.header}usage:{a.end}\n    make <recipe>\n    make help <recipe>\n\nendef\n.DEFAULT_GOAL = help\ninclude $(shell git rev-parse --show-toplevel)/task.mk\n
"}]} \ No newline at end of file diff --git a/sitemap.xml.gz b/sitemap.xml.gz index cb300ff1624a631bbf268b9006ef37d42f4cb41b..1f4e86bea3baf6da0a27b6e132614573177c3884 100644 GIT binary patch delta 13 Ucmeyx_=}NMzMF$%|3ucW03wS800000 delta 13 Ucmeyx_=}NMzMF$%+C