mike/biboumi
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rename the build directory in the e2e docker doc

Browse Source 
To avoid conflicting with the “host” build/ directory. This way we don’t
need to remove/empty the build/ directory beforehand, etc.
This commit is contained in:
louiz’
2019-11-13 22:14:18 +01:00
parent acc0458054
commit 0cb62d993b
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/developer.rst
+2 -2
View File
@@ -71,7 +71,7 @@ created):
.. code-block:: bash .. code-block:: bash
:caption: Configure and build biboumi from inside the container :caption: Configure and build biboumi from inside the container
docker exec biboumi-e2e sh -c "cd biboumi && mkdir build/ && cd build/ && cmake .." docker exec biboumi-e2e sh -c "cd biboumi && mkdir docker-build/ && cd docker-build/ && cmake .."
This is needed (only once), because if you configure it from your host This is needed (only once), because if you configure it from your host
machine, then the paths generated by cmake will be all wrong when you try machine, then the paths generated by cmake will be all wrong when you try
@@ -80,7 +80,7 @@ to compile from inside the container and nothing will work.
.. code-block:: bash .. code-block:: bash
:caption: Re-compile and run the test suite inside the container :caption: Re-compile and run the test suite inside the container
docker exec biboumi-e2e sh -c "cd biboumi/build && make e2e" docker exec biboumi-e2e sh -c "cd biboumi/docker-build && make e2e"
This should now build everything correctly, and run the test suite. If you This should now build everything correctly, and run the test suite. If you
want to re-run it again after you edited something in your source tree, want to re-run it again after you edited something in your source tree,