diff options
-rw-r--r-- | docs/contracts.rst | 4 | ||||
-rw-r--r-- | docs/frequently-asked-questions.rst | 2 | ||||
-rw-r--r-- | docs/miscellaneous.rst | 4 |
3 files changed, 6 insertions, 4 deletions
diff --git a/docs/contracts.rst b/docs/contracts.rst index b0d24c67..1fd23732 100644 --- a/docs/contracts.rst +++ b/docs/contracts.rst @@ -891,8 +891,8 @@ custom types without the overhead of external function calls: As the compiler cannot know where the library will be deployed at, these addresses have to be filled into the -final bytecode by a linker (see [Using the Commandline -Compiler](#using-the-commandline-compiler) on how to use the +final bytecode by a linker +(see :ref:`commandline-compiler`) on how to use the commandline compiler for linking). If the addresses are not given as arguments to the compiler, the compiled hex code will contain placeholders of the form `__Set______` (where diff --git a/docs/frequently-asked-questions.rst b/docs/frequently-asked-questions.rst index 65b5afdf..a081fc16 100644 --- a/docs/frequently-asked-questions.rst +++ b/docs/frequently-asked-questions.rst @@ -2,7 +2,7 @@ Frequently Asked Questions ########################### -This list was originally compiled by [fivedogit](mailto:fivedogit@gmail.com). +This list was originally compiled by `fivedogit <mailto:fivedogit@gmail.com>`_. *************** diff --git a/docs/miscellaneous.rst b/docs/miscellaneous.rst index e1c9f4aa..4a7b8438 100644 --- a/docs/miscellaneous.rst +++ b/docs/miscellaneous.rst @@ -97,6 +97,8 @@ even though the instructions contained a jump in the beginning. .. index:: ! commandline compiler, compiler;commandline, ! solc, ! linker +.. _commandline-compiler: + ****************************** Using the Commandline Compiler ****************************** @@ -119,7 +121,7 @@ files reside, so things like `import "/etc/passwd";` only work if you add `=/` a If there are multiple matches due to remappings, the one with the longest common prefix is selected. -If your contracts use [libraries](#libraries), you will notice that the bytecode contains substrings of the form `__LibraryName______`. You can use `solc` as a linker meaning that it will insert the library addresses for you at those points: +If your contracts use :ref:`libraries <libraries>`, you will notice that the bytecode contains substrings of the form `__LibraryName______`. You can use `solc` as a linker meaning that it will insert the library addresses for you at those points: Either add `--libraries "Math:0x12345678901234567890 Heap:0xabcdef0123456"` to your command to provide an address for each library or store the string in a file (one library per line) and run `solc` using `--libraries fileName`. |