talexander
/
freebsd_amp_hwpstate
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
freebsd_amp_hwpstate/share/mk/bsd.port.subdir.mk

151 lines
2.7 KiB
Makefile
Raw Normal View History

I had to bite the bullet: There's now a port.subdir.mk that does the right thing with recursive build, configure, bundle or extract targets. Reviewed by: Submitted by:
1994-08-22 10:46:38 +00:00
# from: @(#)bsd.subdir.mk 5.9 (Berkeley) 2/1/91
Thanks for the overwhelming response (which can be only summarized by the word: "zilch"). I guess the only way to get people try and comment on these kind of things is to shove it down their throat.... ;) Anyway, here's a set of changes required for auto-generation of READMEs in ports directories. Necessary changes and additions of templates to the ports tree will follow shortly. Eventually I'll commit all the generated READMEs to the tree, but that will be in the rather distant future. For now, I encourage anyone with a -current systam and a matching ports tree to do a "make readmes" at the top level and see what they get. Next step will be to add pkg/{COMMENT,DESCR} to all the categories.
1996-04-01 11:13:00 +00:00
# $Id: bsd.port.subdir.mk,v 1.12 1996/03/24 00:41:10 wosch Exp $
I had to bite the bullet: There's now a port.subdir.mk that does the right thing with recursive build, configure, bundle or extract targets. Reviewed by: Submitted by:
1994-08-22 10:46:38 +00:00
.MAIN: all
Add support for DEBUG_FLAGS. If you say something like: make DEBUG_FLAGS=-g2 You can compile something for debugging at debugging level 2. It will also take care not to strip the resulting executable(s).
1994-09-16 14:30:25 +00:00
.if !defined(DEBUG_FLAGS)
I had to bite the bullet: There's now a port.subdir.mk that does the right thing with recursive build, configure, bundle or extract targets. Reviewed by: Submitted by:
1994-08-22 10:46:38 +00:00
STRIP?= -s
Add support for DEBUG_FLAGS. If you say something like: make DEBUG_FLAGS=-g2 You can compile something for debugging at debugging level 2. It will also take care not to strip the resulting executable(s).
1994-09-16 14:30:25 +00:00
.endif
I had to bite the bullet: There's now a port.subdir.mk that does the right thing with recursive build, configure, bundle or extract targets. Reviewed by: Submitted by:
1994-08-22 10:46:38 +00:00
Add fetch-list command for Rod Use ECHO_MSG macro for printing "===>" line things so that I can now turn those OFF when I don't want them.
1995-03-21 03:59:13 +00:00
ECHO_MSG?= echo
I had to bite the bullet: There's now a port.subdir.mk that does the right thing with recursive build, configure, bundle or extract targets. Reviewed by: Submitted by:
1994-08-22 10:46:38 +00:00
_SUBDIRUSE: .USE
@for entry in ${SUBDIR}; do \
Add support to miss out ``DUDS'' subdirectories. See thread in freebsd-ports for more.
1995-03-03 23:30:32 +00:00
OK=""; \
for dud in $$DUDS; do \
if [ $${dud} = $${entry} ]; then \
OK="false"; \
Add fetch-list command for Rod Use ECHO_MSG macro for printing "===>" line things so that I can now turn those OFF when I don't want them.
1995-03-21 03:59:13 +00:00
${ECHO_MSG} "===> ${DIRPRFX}$${entry} skipped"; \
Add support to miss out ``DUDS'' subdirectories. See thread in freebsd-ports for more.
1995-03-03 23:30:32 +00:00
fi; \
done; \
if [ "$$OK" = "" ]; then \
if test -d ${.CURDIR}/$${entry}.${MACHINE}; then \
Add fetch-list command for Rod Use ECHO_MSG macro for printing "===>" line things so that I can now turn those OFF when I don't want them.
1995-03-21 03:59:13 +00:00
${ECHO_MSG} "===> ${DIRPRFX}$${entry}.${MACHINE}"; \
Add support to miss out ``DUDS'' subdirectories. See thread in freebsd-ports for more.
1995-03-03 23:30:32 +00:00
edir=$${entry}.${MACHINE}; \
cd ${.CURDIR}/$${edir}; \
else \
Add fetch-list command for Rod Use ECHO_MSG macro for printing "===>" line things so that I can now turn those OFF when I don't want them.
1995-03-21 03:59:13 +00:00
${ECHO_MSG} "===> ${DIRPRFX}$$entry"; \
Add support to miss out ``DUDS'' subdirectories. See thread in freebsd-ports for more.
1995-03-03 23:30:32 +00:00
edir=$${entry}; \
cd ${.CURDIR}/$${edir}; \
fi; \
${MAKE} ${.TARGET:realinstall=install} \
DIRPRFX=${DIRPRFX}$$edir/; \
I had to bite the bullet: There's now a port.subdir.mk that does the right thing with recursive build, configure, bundle or extract targets. Reviewed by: Submitted by:
1994-08-22 10:46:38 +00:00
fi; \
done
${SUBDIR}::
@if test -d ${.TARGET}.${MACHINE}; then \
cd ${.CURDIR}/${.TARGET}.${MACHINE}; \
else \
cd ${.CURDIR}/${.TARGET}; \
fi; \
${MAKE} all
.if !target(all)
all: _SUBDIRUSE
.endif
Remove obsolete bundle target, add new fetch target.
1994-09-14 16:42:37 +00:00
.if !target(fetch)
fetch: _SUBDIRUSE
Whoops - left out the package rule! Submitted by: jkh
1994-08-22 13:02:16 +00:00
.endif
Add fetch-list command for Rod Use ECHO_MSG macro for printing "===>" line things so that I can now turn those OFF when I don't want them.
1995-03-21 03:59:13 +00:00
.if !target(fetch-list)
fetch-list: _SUBDIRUSE
.endif
Remove obsolete bundle target, add new fetch target.
1994-09-14 16:42:37 +00:00
.if !target(package)
package: _SUBDIRUSE
New bsd.port.subdir.mk file for use by ports. This groks all the special ports building targets and will recurse properly. Sorry, Julian E - no fancy prompts, just recursion! :-) Added a `bundle' target. Purpose is as follows: You want to give someone a complete tree sans distfiles (for sticking on CDROM perhaps?) but the difficulty there is that the first time the user types `make clean', all the unpacked sources are gone again. Typing `make bundle' recreates the original distfile if it can, so someone can "back up" their unpacked tree easily with one command. Whoops, just thought of something - it should warn if you configured the working source. Ok, next commit! :) Submitted by: jkh
1994-08-22 11:20:07 +00:00
.endif
I had to bite the bullet: There's now a port.subdir.mk that does the right thing with recursive build, configure, bundle or extract targets. Reviewed by: Submitted by:
1994-08-22 10:46:38 +00:00
.if !target(extract)
extract: _SUBDIRUSE
.endif
.if !target(configure)
configure: _SUBDIRUSE
.endif
.if !target(build)
build: _SUBDIRUSE
.endif
.if !target(clean)
clean: _SUBDIRUSE
.endif
.if !target(depend)
depend: _SUBDIRUSE
.endif
Add describe target support.
1995-01-03 11:52:01 +00:00
.if !target(describe)
describe: _SUBDIRUSE
.endif
Add reinstall.
1994-11-17 16:02:56 +00:00
.if !target(reinstall)
reinstall: _SUBDIRUSE
.endif
I had to bite the bullet: There's now a port.subdir.mk that does the right thing with recursive build, configure, bundle or extract targets. Reviewed by: Submitted by:
1994-08-22 10:46:38 +00:00
.if !target(install)
.if !target(beforeinstall)
beforeinstall:
.endif
.if !target(afterinstall)
afterinstall:
.endif
install: afterinstall
afterinstall: realinstall
realinstall: beforeinstall _SUBDIRUSE
.endif
.if !target(tags)
tags: _SUBDIRUSE
.endif
bsd.port.mk: missing semicolon added bsd.port.subdir.mk: added check-md5 as target
1994-12-17 20:50:44 +00:00
Rename check-md5 target to checksum. Submitted by: gpalmer
1995-01-05 01:46:05 +00:00
.if !target(checksum)
checksum: _SUBDIRUSE
bsd.port.mk: missing semicolon added bsd.port.subdir.mk: added check-md5 as target
1994-12-17 20:50:44 +00:00
.endif
Thanks for the overwhelming response (which can be only summarized by the word: "zilch"). I guess the only way to get people try and comment on these kind of things is to shove it down their throat.... ;) Anyway, here's a set of changes required for auto-generation of READMEs in ports directories. Necessary changes and additions of templates to the ports tree will follow shortly. Eventually I'll commit all the generated READMEs to the tree, but that will be in the rather distant future. For now, I encourage anyone with a -current systam and a matching ports tree to do a "make readmes" at the top level and see what they get. Next step will be to add pkg/{COMMENT,DESCR} to all the categories.
1996-04-01 11:13:00 +00:00
.if !target(readmes)
readmes: readme _SUBDIRUSE
.endif
.if !target(readme)
readme:
@rm -f README.html
@make README.html
.endif
PORTSDIR ?= /usr/ports
TEMPLATES ?= ${PORTSDIR}/templates
.if defined(PORTSTOP)
README= ${TEMPLATES}/README.top
.else
README= ${TEMPLATES}/README.category
.endif
README.html:
@echo "===> Creating README.html"
@> $@.tmp
.for entry in ${SUBDIR}
.if defined(PORTSTOP)
@echo -n '<a href="'${entry}/README.html'">${entry}</a>: ' >> $@.tmp
.else
@echo -n '<a href="'${entry}/README.html'">'"`cd ${entry}; make package-name`</a>: " >> $@.tmp
.endif
.if exists(${entry}/pkg/COMMENT)
@cat ${entry}/pkg/COMMENT >> $@.tmp
.else
@echo "(no description)" >> $@.tmp
.endif
.endfor
@sort -t '>' +1 -2 $@.tmp > $@.tmp2
@cat ${README} | \
sed -e 's%%CATEGORY%%'`echo ${.CURDIR} | sed -e 's.*/\([^/]*\)$$\1'`'g' \
-e '/%%DESCR%%/r${.CURDIR}/pkg/DESCR' \
-e '/%%DESCR%%/d' \
-e '/%%SUBDIR%%/r$@.tmp2' \
-e '/%%SUBDIR%%/d' \
> $@
@rm -f $@.tmp $@.tmp2