Seth Woolley's Man Viewer

aeb(1) - -Build - build a change - man 1 aeb

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

 -Build(1)                                                           -Build(1)



NAME
        -Build - build a change

SYNOPSIS
       -Build [ option...  ][ filename...  ]
       -Build -List [ option...  ]
       -Build -Help

DESCRIPTION
       The  -Build command is used to build a project.  The project configura-
       tion file(1,n) is consulted for the appropriate build command, and that com-
       mand  is executed (see the build_ command and integration_build_command
       fields in(1,8) aepconf(5) for more information.)  Output of the  command  is
       automatically  logged  to  the .log file(1,n) at the root of the development
       directory tree.  The build command will be executed  with  its  current
       directory  being the root of the development directory, irrespective of
       there the  -Build command was executed.

       If the change is in(1,8) the  being  integrated  state,  references  to  the
       development  directory, above, should be read(2,n,1 builtins) as the integration direc-
       tory.  Integration build commands are executed with the user and  group
       set(7,n,1 builtins)  to the project's owning user and group.  That is, it is not neces-
       sary for an integrator to log in(1,8) as someone else, the  project  account
       for instance, in(1,8) order to do an integration.

   Process Side Effects
       This  command  will cancel any test registrations, because building the
       project logically invalidates them.  If the project configuration  file(1,n)
       was deleted, any diff registration will also be canceled.

   Notification
       The  actions  of  the  command are controlled by the build_ command and
       integration_build_command fields of the project config(1,5) file.  See  aep-
       conf(3,5)(5) for more information.

PARTIAL BUILD
       If files are named(5,8) on the command line, these files are appended to the
       build command.  This is known as a partial build.  Partial  builds  are
       not legal in(1,8) the being integrated state, but can often be useful in(1,8) the
       being developed state.  Partial builds are not recorded in(1,8)  the  change
       status,  because builds are decoupled from aegis it is not possible for
       aegis to know if(3,n) any set(7,n,1 builtins) of partial builds  is  equivalent  to  a  full
       build.

       Warning:  no  change  state  lock  is taken for a partial build, only a
       baseline read(2,n,1 builtins) lock.

OPTIONS
       The following options are understood:

       name=value
               Command line arguments of this form are assumed to be  variable
               assignments  for  the  build  tool.   They  are  passed through
               unchanged.  They imply a partial build.

       -MINImum
               This option may be used to request a source-only  development_-
               directory_style.   This is useful if(3,n) you want to simulate some-
               thing like aeib -minimum in(1,8) the  development  directory.   This
               option  is  only  meaningful  if(3,n) development_directory_style is
               being used.  If the change is in(1,8) the  being  integrated  state,
               and  the  developer specified -MINImum when issuing the  -Inte-
               grate_Begin command, then this option is set(7,n,1 builtins) by default.

       -Verify_Symbolic_Links
               This option may be used to request a scan for  up-to-date  sym-
               bolic  links  before and after the build.  (Actually, this does
               the updating  for  all  development_directory_style  variants.)
               This  is  the  default.   See also the ``symbolic_links_prefer-
               ence'' field of aeuconf(5).  This option is not  meaningful  if(3,n)
               development_directory_style is not being used.

       -Assume_Symbolic_Links
               This  option may be used to request no scan for up-to-date sym-
               bolic links before and after the build, this is useful when you
               have  just  done  a  build and you know they are already up-to-
               date.   (Actually,  this  suppresses  all  updating   for   all
               development_directory_style  variants.)   See  also  the ``sym-
               bolic_links_preference'' field of aeuconf(5).  This  option  is
               not  meaningful  if(3,n)  development_directory_style  is  not being
               used.

RECOMMENDED ALIAS
       The recommended alias for this command is
       csh%    alias aeb ' -b \!* -v'
       sh$     aeb(){ -b "$@" -v}

ERRORS
       It is an error(8,n) if(3,n) the change is not assigned to the current user.
       It is an error(8,n) if(3,n) the change is not in(1,8) one of the  being  developed  or
       being integrated states.
       It is an error(8,n) if(3,n) a partial build is requested and the change is in(1,8) the
       being integrated state.

SEE ALSO
       aedb(1) begin development of a change

       aecp(1) file(1,n) copy also takes a baseline read(2,n,1 builtins) lock (non-exclusive)

       aeib(1) begin integration of a change

       aeipass(1)
               integrate pass takes a baseline write(1,2) lock (exclusive)

       aet(1)  run tests

       aemetrics(5)
               metrics values file(1,n) format

       aepconf(5)
               project configuration file(1,n) format

       aeuconf(5)
               user configuration file(1,n) format



                               Reference Manual                      -Build(1)

References for this manual (incoming links)