Debugging a Recipe

A-A-P home page | A-A-P Recipe Executive
--- | ---
Prev |  | Next

# Chapter 21. Debugging a Recipe

The log file shows what happened while A-A-P was executing. Often you can figure out what went wrong by looking at the messages. The log file is named "AAP/log". It is located in the directory of the main recipe. If you executed aap again and now want to see the previous log, it is named "AAP/log1". Older logs are "AAP/log2", "AAP/log3", etc. This goes up to "AAP/log9".

    MESSAGES

    The kind of messages given can be changed with the MESSAGE variable.  It is a
    list of message types for which the message is actually displayed:
    	all		everything
    	error		error messages
    	warning		warnings
    	depend		dependencies, the reasoning about what to build
    	info		general info (file copy/delete, up/downloads)
    	extra		extra info (why something was done)
    	system		system (shell) commands
    	changedir	changing directories

    The command line arguments "-v" and "-s" can be used to make the most often
    used selections:

    	argument	MESSAGE
    	(nothing)	error,info,system
    	-v --verbose	all
    	-s --silent	error

    Other values can be assigned at the command line.  For example, to only see
    error and dependency messages:

    	aap MESSAGE=error,depend  (other arguments)

    Don't forget that excluding "error" means that no error messages are given!

    No matter what messages are displayed, all messages are written in the log
    file.  This can be used afterwards to see what actually happened.  The name of
    the log file is "aap/log".  This is located relative to the main recipe.
    Older log files are also remembered.  The previous log is "aap/log1".  The
    oldest log is "aap/log9".

Prev | Contents | Next
Porting an Application | Up | Differences from make