Ignore:
Timestamp:
06/30/2020 05:45:38 PM (16 months ago)
Author:
Ken Moffat <ken@…>
Branches:
10.0, 10.1, 11.0, ken/refactor-virt, lazarus, qt5new, trunk, xry111/git-date, xry111/git-date-for-trunk, xry111/git-date-test
Children:
eb7de89
Parents:
693f28e1
Message:

Rust: explain how to (mostly) restrict how many processors it wants to use.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@23349 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • general/prog/rust.xml

    r693f28e1 r5ce1bdb  
    102102      all available processors, although it does not scale well and often falls
    103103      back to just using one core while waiting for a library to compile.
     104      However it can be mostly limited to a specified number of processors by
     105      a combination of adding the switch <literal>--jobs &lt;N&gt;</literal>
     106      (e.g. '--jobs 4' to limit to 4 processors) on each invocation of
     107      <command>python3 ./x.py</command> <emphasis>and</emphasis> using an
     108      environment variable <envar>CARGO_BUILD_JOBS=&lt;N&gt;</envar>. At the
     109      moment this is not effective when some of the rustc tests are run.
    104110    </para>
    105111
Note: See TracChangeset for help on using the changeset viewer.