| Christopher Wiley | b2bec59 | 2014-03-27 15:33:28 -0700 | [diff] [blame] | 1 | Some common workflows for developing with buffet: |
| 2 | |
| 3 | # Tell portage that you'd like to make local changes to Buffet: |
| 4 | cros_workon start --board=${BOARD} platform2 |
| 5 | |
| 6 | # Edit files in platform2/buffet/ |
| 7 | vim ... |
| 8 | |
| 9 | # Compile and install those changes into the chroot: |
| 10 | USE=buffet emerge-<board> platform2 |
| 11 | |
| 12 | # Compile and run buffet unittests |
| 13 | USE=buffet P2_TEST_FILTER="buffet::*" FEATURES=test emerge-<board> platform2 |
| 14 | |
| 15 | # Deploy the most recently built version of buffet to a DUT: |
| 16 | cros deploy --board=${BOARD} <remote host> platform2 |
| Alex Vakulenko | a3062c5 | 2014-04-21 17:05:51 -0700 | [diff] [blame] | 17 | |
| 18 | #To enable additional debug logging in buffet daemon, run it as: |
| 19 | # buffet --v=<level>, where <level> is verbosity level of debug info: |
| 20 | # 1 - enable additional tracing of internal object construction and destruction |
| 21 | # 2 - add tracing of request and response data sent over HTTP (beware of |
| 22 | # privacy concerns). |
| 23 | # 3 - enable low-level CURL tracing for HTTP communication. |
| 24 | buffet --v=2 |
