docs/linux_eclipse_dev.md - Issue 2551513002: Fix spelling mistakes in //docs.

Side by Side Diff: docs/linux_eclipse_dev.md

Issue 2551513002: Fix spelling mistakes in //docs. (Closed)

Patch Set: Undo beng->being Created 4 years ago

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

Jump to:

« no previous file with comments | « docs/linux_debugging.md ('k') | docs/linux_gtk_theme_integration.md » ('j') | no next file with comments »

OLD	NEW
1 # Linux Eclipse Dev	1 # Linux Eclipse Dev

2	2

3 Eclipse can be used on Linux (and probably Windows and Mac) as an IDE for	3 Eclipse can be used on Linux (and probably Windows and Mac) as an IDE for

4 developing Chromium. It's unpolished, but here's what works:	4 developing Chromium. It's unpolished, but here's what works:

5	5

6 * Editing code works well (especially if you're used to it or Visual Studio).	6 * Editing code works well (especially if you're used to it or Visual Studio).

7 * Navigating around the code works well. There are multiple ways to do this	7 * Navigating around the code works well. There are multiple ways to do this

8 (F3, control-click, outlines).	8 (F3, control-click, outlines).

9 * Building works fairly well and it does a decent job of parsing errors so	9 * Building works fairly well and it does a decent job of parsing errors so

10 that you can click and jump to the problem spot.	10 that you can click and jump to the problem spot.

(...skipping 276 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
287 After fighting with with a number of approaches, I've found the below to work	287 After fighting with with a number of approaches, I've found the below to work

288 best for me.	288 best for me.

289	289

290 1. From a shell in your src directory, run	290 1. From a shell in your src directory, run

291 `gn gen --ide=eclipse out/Debug_gn/' (replacing Debug_gn with the output dir ectory you normally use when building).	291 `gn gen --ide=eclipse out/Debug_gn/' (replacing Debug_gn with the output dir ectory you normally use when building).

292 1. This generates <project root>/out/Debug_gn/eclipse-cdt-settings.xml whic h	292 1. This generates <project root>/out/Debug_gn/eclipse-cdt-settings.xml whic h

293 is used below.	293 is used below.

294 1. This creates a single list of include directories and preprocessor	294 1. This creates a single list of include directories and preprocessor

295 definitions to be used for all source files, and so is a little	295 definitions to be used for all source files, and so is a little

296 inaccurate. Here are some tips for compensating for the limitations:	296 inaccurate. Here are some tips for compensating for the limitations:

297 1. If you care about blink, move 'third\_party/Webkit/Source' to the	297 1. If you care about blink, move 'third\_party/WebKit/Source' to the

298 top of the list to better resolve ambiguous include paths (eg.	298 top of the list to better resolve ambiguous include paths (eg.

299 `config.h`).	299 `config.h`).

300 1. Import paths and symbols	300 1. Import paths and symbols

301 1. Right click on the project and select Properties > C/C++ General > Paths	301 1. Right click on the project and select Properties > C/C++ General > Paths

302 and Symbols	302 and Symbols

303 1. Click Restore Defaults to clear any old settings	303 1. Click Restore Defaults to clear any old settings

304 1. Click Import Settings... > Browse... and select	304 1. Click Import Settings... > Browse... and select

305 `<project root>/out/Debug/eclipse-cdt-settings.xml`	305 `<project root>/out/Debug/eclipse-cdt-settings.xml`

306 1. Click the Finish button. The entire preferences dialog should go away.	306 1. Click the Finish button. The entire preferences dialog should go away.

307 1. Right click on the project and select Index > Rebuild	307 1. Right click on the project and select Index > Rebuild

(...skipping 88 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
396 ### Additional tips	396 ### Additional tips

397	397

398 1. Mozilla's	398 1. Mozilla's

399 [Eclipse CDT guide](https://developer.mozilla.org/en-US/docs/Eclipse_CDT)	399 [Eclipse CDT guide](https://developer.mozilla.org/en-US/docs/Eclipse_CDT)

400 is helpful:	400 is helpful:

401 1. For improved performance, I use medium-granularity projects (eg. one for	401 1. For improved performance, I use medium-granularity projects (eg. one for

402 WebKit/Source) instead of putting all of 'src/' in one project.	402 WebKit/Source) instead of putting all of 'src/' in one project.

403 1. For working in Blink (which uses WebKit code style), feel free to use	403 1. For working in Blink (which uses WebKit code style), feel free to use

404 [this](https://drive.google.com/file/d/0B2LVVIKSxUVYM3R6U0tUa1dmY0U/view?usp =sharing)	404 [this](https://drive.google.com/file/d/0B2LVVIKSxUVYM3R6U0tUa1dmY0U/view?usp =sharing)

405 code-style formatter XML profile	405 code-style formatter XML profile

OLD	NEW