Content-type: text/html Manpage of PUPSCONF

PUPSCONF

Section: PUPS build tools (1)
Updated: 22nd February 2005
Index Return to Main Contents

NAME

PUPSCONF - Makefile configuration facility for PUPS

SYNOPSIS

pupsconf ! Makefile configuration file name !! Template makefile name !! Makefile name [ dserial serial number ] | [ sdongle dongle file name | dongle key ] >& <log file>

DESCRIPTION

pupsconf(1) is a utility similar to gnu configure, configure(1) which generates makefiles from a makefile template and a configuration file which contains system dependant makefile fragments to be subsituted in the makefile. pupsconfig(1) is both more simple and less versatile than configure(1), but is useful for generating makefiles for machines/environments which require different CFLAGS and LDFLAG definitions. The configuration information is stored in the directory ./config and is of the form:

# comment <macro dummy name to be subsituted 1> <substition string 1>

end

If the dummy name is not to be subsituted the substitution string "no" or "none" should be used. The end statement at the end of the configuration file is mandatory.

OPTIONS

These options are only valid if pupsconf(1) has been built with secure mode extensions.

dserial disk serial number tells pupsconf(1) to use the hard disk serial number as the software build authentication token when generating makefile. If a serial number is specified, that is used (enable secure remote build). If not, the serial number of the disk the software is to be built on is used. This option and sdongle are mutually exclusive.

sdongle dongle file name | dongle key tells puspconf(1) to use either the (random) inode of the supplied dongle file or the supplied dongle key as the authentication token when generating makefile. If a dongle file name is specified, it is assumed to be on the disk being used for the build: dongle key can refer to an appropriate file on the local build disk, or a remote disk, which means that this option can be used for remote builds. sdongle and dserial are mutually exclusive.

EXAMPLE MACRO FILE

# This is the name of the macro
TARGET_CFLAGS

#This is its body
-verbose -DHAVE_MACROS

# End of macro definitions
end

FILES

Makefile.in
Makefile
config_file

ENVIRONMENT VARIABLES

PUPSCONF gives the name of the directory to be searched for the configuration file.

If secure build mode extensions are enabled USE_DISK_SERIAL disk_serial tells pupsconf(1) to use the disk serial number as the secure authentication token for building the software. If disk_serial is specified, it is used as the disk serial, otherwise the build disk is probed for its serial number. This environmental option and USE_SOFT_DONGLE are mutually exclusive. Note they disk serial number must be pre-encrypted. Thus, it is generated by running the hdid(1) command on the target host: hdid -ecrypt <disk device>

USE_SOFT_DONGLE dongle file name | dongle key tells pupsconf(1) to use the (randomised) inode of the specified dongle file or the specified dongle key as the secure authentication token for building the software. The dongle file is assumed to be on the build disk, but the dongle key can refer to an appropriate file anywhere, permitting soft dongles to be used for remote builds. This environmental option and USE_DISK_SERIAL are mutually exclusive. Note the dongle key must be specified in hex. This key is obtained by running sdongle(1) on the target host.

BUGS

At present the disk serial authentication mechanism only works for ATAPI not SCSI disks.

COPYRIGHT

PROGRAMMER

M.A. O'Neill.

This document was created by man2html, using the manual pages.
Time: 13:53:35 GMT, January 11, 2008