summaryrefslogtreecommitdiffstats
path: root/tools/merge-event-log-tags.py
Commit message (Collapse)AuthorAgeFilesLines
* py3: update all the thingsAnthony King2016-01-041-1/+1
| | | | Change-Id: I5e11b46b7c2f7f8760d6c0e713ca99c1e88b7cd3
* py3: merge-event-log-tagsAnthony King2016-01-041-13/+26
| | | | Change-Id: I875d48c67efa129e800bcc834f41d39fc25a62e4
* fix merge-event-log-tags.py deprecation warningDoug Zongker2012-09-201-2/+5
| | | | | | | Prefer using the hashlib module if it's available, instead of the deprecated md5 module. Change-Id: Id5e50af125ae47f34d011d8612059424472c7c3f
* Fix event-log-tags so we don't rebuild framework.jar because of an installclean.Joe Onorato2010-07-141-8/+27
| | | | | | | | Produce an event logs tag file for everything we know about, in order to properly allocate numbers. Then produce a file that's filtered for what's going to be installed. Change-Id: Id0778aec0b4d045e8ff91ba2c9c8265e860eaba5
* Allow explicit and implicit numbering of the same tag.Dan Egnor2010-03-171-0/+6
| | | | Change-Id: I59c24cc211250da7e0aed9e0b0aa16517fd72d55
* allow java eventlogtags to be generated for packages that aren't includedDoug Zongker2010-02-171-1/+1
| | | | | | | | | If there are packages that specify logtags being built that aren't included in the product, their logtags won't be included in the merged file. Assign an arbitrary tag number to them so they can be built anyway. Change-Id: I4929016bf289b7a814b48bc51f324c09f500fab1
* allow EventLog tag numbers to be auto-assignedDoug Zongker2010-02-161-12/+65
| | | | | | | | | | | | | | | | | | | | 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
* break up event-log-tags; generate java source files with constantsDoug Zongker2009-12-031-0/+103
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.