aprojbaseline- convert an existing project to or from the baselined state.
aprojbaseline [-lmpvw| -u ] [ project_root ]
aprojbaseline marks the current or specified project as a baseline project, and performs other operations to make it suitable for building delta projects against. These transformations include:
- removing pending (loaded but not compiled) units (unless -p is specified)
- merging delta sublibraries (unless -m is specified)
- removing lock files (unless -l is specified)
- building cache files
- making all files and directories read-only (unless -w is specified).
If aprojbaseline -u is specified, an existing baseline project is "un-baselined":
- cache files are deleted
- write-access is restored (unless -w is specified)
- lock files are restored (unless -l is specified)
You must have write access to all files and directories in the project in order to change its baseline status.
This operation is also provided from within powerada.
Note that this does not automatically update the file named by the POWERADABASELINES environment variable--this must be done manually.
- Prints version, and command line help information.
- Do not delete the lock files which control concurrent access to sublibraries in the project. This is advisable if -w is also specified. When accompanied by -u, has the opposite effect: does not attempt to re-create the lock files, in case they were never deleted in the first place.
- Do not merge delta sublibraries back into each base sublibrary. (Delta sublibraries are created to support write operations into a sublibrary that is currently being read; see alibcompress.) This option is not valid with -u.
- Do not delete pending units from each sublibrary. This is not recommended, since the existence of such units can confuse recompilation computation, since their presence will always cause recompilation of the loaded unit into a subsequent working project. This option is not valid with -u.
- Verbose mode -- print progress messages.
- Do not change the protection of all files and sublibraries to read-only. This is not recommended, as it would allow the use of lower-level tools like ada, aunitmv, etc. to change the contents of a baseline "underneath" other users. On the other hand, it does make the command significantly faster on large projects. When accompanied by -u, this has the opposite effect: no attmpt is made to change the protection unless the project root itself is read-only.
- Indicates that the designated project is already a baseline which should be "unbaselined". Use this with care, as there is no check for the existence of client projects created against this baseline. The options -l and -w have the opposite effect when accompanied by this option.
- The root directory of the project to be (un)baselined
the aprojbaseline program image.
- This must be defined and indicate the powerada/ada95 directory in the PowerAda installation.
- Names a baselines file identifying aliases for baseline projects.
# baseline the project in which the current directory resides:
# unbaseline a project:
aprojbaseline -vu /build1/adaproj
See Problems and Questions at the beginning of this Appendix.