mirror of
https://git.hardenedbsd.org/hardenedbsd/HardenedBSD.git
synced 2024-11-24 09:13:37 +01:00
ce7756fdca
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
|
||
|---|---|---|
| .. | ||
| 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 | ||
| rc.local | ||
| release.conf.sample | ||
| release.sh | ||