Searched hist:"4 afe7cf500c71e278eba5b91192d024b3a211d85" (Results 1 – 2 of 2) sorted by relevance
| /freebsd/release/ |
| H A D | Makefile.vm | diff 4afe7cf500c71e278eba5b91192d024b3a211d85 Thu Jan 22 20:43:05 CET 2015 Glen Barber <gjb@FreeBSD.org> Rename the 'release' target to 'real-release', and
add two targets, 'vm-release' and 'cloudware-release',
that are invoked if WITH_VMIMAGES and WITH_CLOUDWARE
are not empty.
This fixes an issue where 'make release' would not
build the cloud provider targets because CLOUDWARE was
not yet set. [1]
Move the WITH_VMIMAGES and WITH_CLOUDWARE targets to
Makefile.vm.
Note: There is no 'cloudware-install' target yet, since
some of the disk image names may need to be specific to
the provider, so this is probably best handled by the
build scripts.
Reported by: cperciva [1]
MFC after: 1 month
X-MFC-with: r277458
Sponsored by: The FreeBSD Foundation
|
| H A D | Makefile | diff 4afe7cf500c71e278eba5b91192d024b3a211d85 Thu Jan 22 20:43:05 CET 2015 Glen Barber <gjb@FreeBSD.org> Rename the 'release' target to 'real-release', and
add two targets, 'vm-release' and 'cloudware-release',
that are invoked if WITH_VMIMAGES and WITH_CLOUDWARE
are not empty.
This fixes an issue where 'make release' would not
build the cloud provider targets because CLOUDWARE was
not yet set. [1]
Move the WITH_VMIMAGES and WITH_CLOUDWARE targets to
Makefile.vm.
Note: There is no 'cloudware-install' target yet, since
some of the disk image names may need to be specific to
the provider, so this is probably best handled by the
build scripts.
Reported by: cperciva [1]
MFC after: 1 month
X-MFC-with: r277458
Sponsored by: The FreeBSD Foundation
|