summaryrefslogtreecommitdiffstats
path: root/tools/event_log_tags.py
Commit message (Collapse)AuthorAgeFilesLines
* py3: update all the thingsAnthony King2016-01-041-4/+6
| | | | Change-Id: I5e11b46b7c2f7f8760d6c0e713ca99c1e88b7cd3
* check syntax of description field in logtags filesDoug Zongker2011-01-231-0/+8
| | | | | | | | | EventLog.java checks that the field descriptions are bracketed by parens, so we should to in order to avoid a runtime error from a logtag entry with bad syntax. Bug: 3381309 Change-Id: I1d4cbb190da6b81ec0b1f1de9b5bc3f3394d7ec1
* allow EventLog tag numbers to be auto-assignedDoug Zongker2010-02-161-5/+8
| | | | | | | | | | | | | | | | | | | | With this change, you can specify "?" in place of a tag number in a .logtags file and the build system will assign numbers to these tags. (The numbers used shouldn't matter since we translate them back to tag names whenever the logs are read back.) This is pretty straightforward to do: - make merge-event-log-tags.py assign numbers to any tags that specify "?" - make the generated java files depend on the merged output - make java-event-log-tags.py read both the original .logtags and the merged output, and fill in tag numbers for any "?" using the merged version. Change-Id: Icc6ccd705db461d570fc929922a830aa6deaca48
* add option to @hide classes generated from .logtags filesDoug Zongker2009-12-091-0/+12
| | | | | Generate a javadoc @hide comment on the class when "option javadoc_hide true" is specified in the input .logtags file.
* break up event-log-tags; generate java source files with constantsDoug Zongker2009-12-031-0/+112
Construct the /system/etc/event-log-tags file by unioning together any *.logtags files included in LOCAL_SRC_FILES throughout the system (with appropriate error checking for dup tag numbers, etc.) For java packages, generate a java source file from the logtags file for that package that contains static integer constants for each tag name.