jw.build.cmds: Move build.cmds -> cmds.projects
Reorganize the Python module structure. Placing the command classes under jw.cmds.projects instead of jw.build.cmds will allow to add a nested command structure, with the current commands, being mostly related to building software, found below a "projects" toplevel command.
Other conceivable commands could be "package" for packaging, or "distro" for commands wrapping the distribution's package manager.
Signed-off-by: Jan Lindemann <jan@janware.com>
This commit is contained in:
parent
c8c5788aeb
commit
0b83c863a2
43 changed files with 49 additions and 13 deletions
|
|
@ -116,7 +116,7 @@ ifeq ($(TIME),)
|
|||
TIME += -p
|
||||
endif
|
||||
endif
|
||||
PROJECTS_PY = $(TIME) python3 $(JWB_SCRIPT_DIR)/jw-projects.py --prefix $(shell pwd) $(PROJECTS_PY_EXTRA_OPTS)
|
||||
PROJECTS_PY = $(TIME) python3 $(JWB_SCRIPT_DIR)/jw-projects.py --prefix $(shell pwd) $(PROJECTS_PY_EXTRA_OPTS) projects
|
||||
PROJECTS_PY_BUILD = $(PROJECTS_PY) build $(PROJECTS_PY_EXTRA_BUILD_OPTS)
|
||||
|
||||
PGIT_SH := /bin/bash $(JWB_SCRIPT_DIR)/pgit.sh
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue