From cd0ccd099bd6da4d1ed9f0b14a96096b037c3d78 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kamil=20=C5=9Aliwak?= Date: Thu, 24 Jun 2021 19:14:38 +0200 Subject: [PATCH] installing-solidity.rst: Clarify that when using `urls` in Standard JSON with a dockerized compiler it might still be necessary to mount a volume --- docs/installing-solidity.rst | 4 +++- docs/path-resolution.rst | 2 ++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/installing-solidity.rst b/docs/installing-solidity.rst index 7c676ff90..a0857e038 100644 --- a/docs/installing-solidity.rst +++ b/docs/installing-solidity.rst @@ -86,7 +86,9 @@ local folder for input and output, and specify the contract to compile. For exam docker run -v /local/path:/sources ethereum/solc:stable -o /sources/output --abi --bin /sources/Contract.sol You can also use the standard JSON interface (which is recommended when using the compiler with tooling). -When using this interface it is not necessary to mount any directories. +When using this interface it is not necessary to mount any directories as long as the JSON input is +self-contained (i.e. it does not refer to any external files that would have to be +:ref:`loaded by the import callback `). .. code-block:: bash diff --git a/docs/path-resolution.rst b/docs/path-resolution.rst index 2aab72dd5..5848e3f9a 100644 --- a/docs/path-resolution.rst +++ b/docs/path-resolution.rst @@ -104,6 +104,8 @@ The initial content of the VFS depends on how you invoke the compiler: The ``sources`` dictionary becomes the initial content of the virtual filesystem and its keys are used as source unit names. + .. _initial-vfs-content-standard-json-with-import-callback: + #. **Standard JSON (via import callback)** With Standard JSON it is also possible to tell the compiler to use the import callback to obtain