diff options
author | jessicag.feedback <jessicag.feedback@4c0a9323-5329-0410-9bdc-e9ce6186880e> | 2010-08-13 18:49:03 +0000 |
---|---|---|
committer | jessicag.feedback <jessicag.feedback@4c0a9323-5329-0410-9bdc-e9ce6186880e> | 2010-08-13 18:49:03 +0000 |
commit | 25b9371026bad2d8c4e9699eef48069cf29bdcfb (patch) | |
tree | 02f78c496da3eaeebd3dcc87b243e19c3fb0074c /README | |
parent | Add glog external reference to third party. (diff) | |
download | breakpad-25b9371026bad2d8c4e9699eef48069cf29bdcfb.tar.xz |
Update readme and fix glog properties.
git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@644 4c0a9323-5329-0410-9bdc-e9ce6186880e
Diffstat (limited to 'README')
-rw-r--r-- | README | 41 |
1 files changed, 41 insertions, 0 deletions
@@ -1,2 +1,43 @@ Breakpad is a set of client and server components which implement a crash-reporting system. + + +----- +Getting started in 32-bit mode (from trunk) +Configure: CXXFLAGS=-m32 CFLAGS=-m32 CPPFLAGS=-m32 ./configure + Build: make + Test: make check + Install: make install + +If you need to reconfigure your build be sure to run "make distclean" first. + + +----- +To request change review: +0. Get access to a read-write copy of source. + Owners at http://code.google.com/p/google-breakpad/ are able to grant + this access. + +1. Check out a read-write copy of source using instructions at + http://code.google.com/p/google-breakpad/source/checkout + +2. Make changes. Build and test your changes. + For core code like processor use methods above. + For linux/mac/windows, there are test targets in each project file. + +3. Download http://codereview.appspot.com/static/upload.py + +4. Run upload.py from the 'src' directory: + upload.py --server=breakpad.appspot.com + + You will be prompted for credential and a description. + +5. At http://breakpad.appspot.com you'll find your issue listed; click on it, + and select Publish+Mail, and enter in the code reviewer and CC + google-breakpad-dev@googlegroups.com + +6. When applying code review feedback, specify the '-i' option when running + upload.py again and pass the issue number so it updates the existing issue, + rather than creating a new one. + Be sure to rerun upload.py from the same directory as you did for previous + uploads to allow for proper diff calculations. |