[GN]: Support for loadable modules

tools/gn/docs/language.md

 # GN Language and Operation
 
 [TOC]
 
 ## Introduction
 
 This page describes many of the language details and behaviors.
 
 ### Use the built-in help!
 
@@ skipping 358 matching lines @@
 other targets. The built-in target types (see `gn help <targettype>` for
 more help) are:
 
   * `action`: Run a script to generate a file.
   * `action_foreach`: Run a script once for each source file.
   * `component`: Configurable to be another type of library.
   * `executable`: Generates an executable file.
   * `group`: A virtual dependency node that refers to one or more other
     targets.
   * `shared_library`: A .dll or .so.
+  * `loadable_module`: An .so loadable only at runtime.

[brettw, 2015/10/13 23:13:32]

Can you write ".dll or .so"

[Bons, 2015/10/13 23:30:52]

Done.

   * `source_set`: A lightweight virtual static library (usually
     preferrable over a real static library since it will build faster).
   * `static_library`: A .lib or .a file (normally you'll want a
-    source\_set instead).
+    `source_set` instead).
 
 You can extend this to make custom target types using templates (see below).
 
 ## Configs
 
 Configs are named objects that specify sets of flags, include
 directories, and defines. They can be applied to a target and pushed to
 dependent targets.
 
 To define a config:
@@ skipping 332 matching lines @@
 settings which work a bit differently in Blaze. This is partially to
 make conversion from the existing GYP code easier, and the GYP
 constructs generally offer more fine-grained control (which is either
 good or bad, depending on the situation).
 
 GN also uses GYP names like "sources" instead of "srcs" since
 abbreviating this seems needlessly obscure, although it uses Blaze's
 "deps" since "dependencies" is so hard to type. Chromium also compiles
 multiple languages in one target so specifying the language type on the
 target name prefix was dropped (e.g. from `cc_library`).