README - Issue 1357773004: [Docs] add markdown docs (converted from Wiki)

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: README

Issue 1357773004: [Docs] add markdown docs (converted from Wiki) (Closed) Base URL: https://chromium.googlesource.com/breakpad/breakpad.git@master

Patch Set: whoops' Created 5 years, 3 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

OLD	NEW
	(Empty)
1 Breakpad is a set of client and server components which implement a

2 crash-reporting system.

3

4

5 -----

6 Getting started in 32-bit mode (from trunk)

7 Configure: CXXFLAGS=-m32 CFLAGS=-m32 CPPFLAGS=-m32 ./configure

8 Build: make

9 Test: make check

10 Install: make install

11

12 If you need to reconfigure your build be sure to run "make distclean" first.

13

14

15 -----

16 To request change review:

17 0. Get a copy of depot_tools repo.

18 http://dev.chromium.org/developers/how-tos/install-depot-tools

19

20 1. Create a new directory for checking out the source code.

21 mkdir breakpad && cd breakpad

22

23 2. Run the `fetch` tool from depot_tools to download all the source repos.

24 fetch breakpad

25

26 3. Make changes. Build and test your changes.

27 For core code like processor use methods above.

28 For linux/mac/windows, there are test targets in each project file.

29

30 4. Commit your changes to your local repo and upload them to the server.

31 http://dev.chromium.org/developers/contributing-code

32 e.g. git commit ... && git cl upload ...

33 You will be prompted for credential and a description.

34

35 5. At https://codereview.chromium.org/ you'll find your issue listed; click on

36 it, and select Publish+Mail, and enter in the code reviewer and CC

37 google-breakpad-dev@googlegroups.com

OLD	NEW

« no previous file with comments | « no previous file | README.md » ('j') | no next file with comments »