Colin Percival ce7756fdca release: make dependencies, not recursive make ... For historical reasons, the vm-release and cloudware-release targets were written as recursive makes of ${VMTARGETS} and ${CLOUDTARGETS}; this worked fine until we started running `make release -jN` and had both VM and cloud targets depending on ${QEMUTGT}, at which point things exploded when we tried to build the port twice at the same time. Switch vm-release and cloudware-release to have make dependencies on their individual components; this way a single make process runs and is aware of the duplicate dependency (and only runs it once). MFC after: 5 days		2024-05-09 00:52:25 -07:00
..
amd64
arm
arm64
i386
packages
pkg_repos
powerpc
riscv
scripts
tools
Makefile
Makefile.azure
Makefile.ec2
Makefile.firecracker
Makefile.gce
Makefile.inc1
Makefile.mirrors
Makefile.vagrant
Makefile.vm	release: make dependencies, not recursive make	2024-05-09 00:52:25 -07:00
rc.local
release.conf.sample
release.sh