Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/etc/etc.acorn26/Makefile.inc

19 lines
508 B
PHP
Raw Normal View History

Use ${HOST_INSTALL_FILE} to put the bootloader in the release tree, rather than cp. This seems to be what everyone else does, and saves problems if the release tree is already part-populated.
2003-03-01 18:36:22 +03:00
# $NetBSD: Makefile.inc,v 1.8 2003/03/01 15:36:22 bjh21 Exp $
New kernel for small systems
2000-07-19 20:49:08 +04:00
#
Rename etc.arm26 -> etc.acorn26
2002-03-25 00:20:38 +03:00
# etc.acorn26/Makefile.inc -- acorn26-specific etc Makefile targets
New kernel for small systems
2000-07-19 20:49:08 +04:00
#
Change the way kernel sets are specified, and make them more consistent. To quote the comment in etc/Makefile that describes how it's done: # This target builds the kernels specified by each port. A port may # specify the following kernels: # # KERNEL_SETS The list of kernels that will be # packaged into sets, named # kern-${kernel}.tgz. These kernels # are also placed in the binary/kernels # area of the release package as # netbsd-${kernel}.gz. # # EXTRA_KERNELS Additional kernels to place in the # binary/kernels area of the release # package as netbsd-${kernel}.gz, but # which are not placed into sets. This # allows a port to provide e.g. a netbootable # installation kernel containing a ramdisk. # # BUILD_KERNELS Additional kernels to build which are # not placed into sets nor into the # binary/kernels area of the release # package. These are typically kernels # that are built for inclusion only in # installation disk/CD-ROM/tape images. #
2001-11-30 01:45:53 +03:00
KERNEL_SETS= GENERIC FOURMEG
- consistency cleanup - ensure INSTALLATION_DIRS contains the appropriate extra directories for a given platform
2002-05-02 19:09:40 +04:00
"make release" in distrib/acorn26 too.
2002-04-19 04:05:25 +04:00
BUILD_KERNELS= INSTALL
When making a release, build the release notes, and copy them and boot26 into the release directory. Also make checksums for boot26.
2002-03-08 02:12:54 +03:00
Put boot26 in the installation/misc directory, since that's where it's documented as being.
2002-03-31 20:02:30 +04:00
INSTALLATION_DIRS+= installation/misc
When making a release, build the release notes, and copy them and boot26 into the release directory. Also make checksums for boot26.
2002-03-08 02:12:54 +03:00
snap_md_post:
# install bootloader into installation directory
Use ${HOST_INSTALL_FILE} to put the bootloader in the release tree, rather than cp. This seems to be what everyone else does, and saves problems if the release tree is already part-populated.
2003-03-01 18:36:22 +03:00
${HOST_INSTALL_FILE} -m ${NONBINMODE} ${DESTDIR}/usr/mdec/boot26,ffa \
Install release files under "${RELEASEDIR}/${MACHINE}/..." instead of "${RELEASEDIR}/...". ${RELEASEDIR} is never cleaned , and ${RELEASEDIR}/${MACHINE} is only cleaned if UPDATE is not defined.
2003-01-03 18:34:30 +03:00
${RELEASEDIR}/${MACHINE}/installation/misc
When making a release, build the release notes, and copy them and boot26 into the release directory. Also make checksums for boot26.
2002-03-08 02:12:54 +03:00
# compute checksums
Install release files under "${RELEASEDIR}/${MACHINE}/..." instead of "${RELEASEDIR}/...". ${RELEASEDIR} is never cleaned , and ${RELEASEDIR}/${MACHINE} is only cleaned if UPDATE is not defined.
2003-01-03 18:34:30 +03:00
${MAKESUMS} -t ${RELEASEDIR}/${MACHINE}/installation/misc 'boot26,ffa'