| | 1 | = Understanding the Results = |
| | 2 | [[TracNav]] |
| | 3 | |
| | 4 | == Everything Works == |
| | 5 | |
| | 6 | If the compilation worked, then the compiler will have produced all of the requested machine profiles and machine dependency files. It will not produce any additional output on the console unless the "verbose" option has been used. If the "verbose" option was active, then each compilation will end with a summary like the following: |
| | 7 | {{{ |
| | 8 | 42 templates |
| | 9 | 441/0/441 compiled, 42/42 built |
| | 10 | 0/0 obj, 42/42 xml, 42/42 dep |
| | 11 | 0 errors, 22128 ms, 119 MB/506 MB heap, 12 MB/112 MB nonheap |
| | 12 | }}} |
| | 13 | Each line reports different statistics: |
| | 14 | 1. The first line shows the number of individual pan templates pass to the compiler for processing. |
| | 15 | 2. The second line shows the number of templates compiled and the number of machine profiles that were built. The three numbers for the compiled templates are: compiled, loaded, and total. The "loaded" templates are pre-compiled sitting in "*.obj" files on disk. |
| | 16 | 3. The third line gives the number of serialized files. The "obj" are the number of templates compiled, the "xml" are the number of machine profiles, and the "dep" are the number of dependency files written to disk. The first number is the number of successfully written files; the second, the total number requested. |
| | 17 | 4. The last line gives the number of errors, total time in milliseconds, maximum used/available heap memory, and the maximum used/available non-heap memory. |
| | 18 | |
| | 19 | These statistics give a good overview of what the compiler has done and provides a good cross-check that the full build was successful. |
| | 20 | |
| | 21 | == Things Go Wrong == |
