esp-idf/docs/en/get-started/toolchain-setup-scratch.rst

.. _get-started-customized-setup:

*************************************
Customized Setup of Toolchain
*************************************

:link_to_translation:`zh_CN:[中文]`

Instead of downloading binary toolchain from Espressif website (see :ref:`get-started-set-up-tools`) you may build the toolchain yourself.

If you can't think of a reason why you need to build it yourself, then probably it's better to stick with the binary version. However, here are some of the reasons why you might want to compile it from source:

- if you want to customize toolchain build configuration
- if you want to use a different GCC version (such as 4.8.5)
- if you want to hack gcc or newlib or libstdc++
- if you are curious and/or have time to spare
- if you don't trust binaries downloaded from the Internet

In any case, here are the instructions to compile the toolchain yourself.

.. toctree::
    :maxdepth: 1

    windows-setup-scratch
    linux-setup-scratch
    macos-setup-scratch
docs: Make CMake build system default, mark GNU Make as legacy option All `-cmake` suffixes are removed Where a GNU Make option is renamed, the `-legacy` suffix is used 2019-06-25 01:26:53 +00:00			`.. _get-started-customized-setup:`
Removed redundant 'Logging to Host' and docs cleaning 2017-08-25 20:35:33 +00:00
docs: Functional renaming commit for CMake-as-default Rename all the files which will be edited substantially in the next commit, without changing their contents Docs will not build for this ocmmit. This is done so that git doesn't decide we renamed xxx-cmake -> xxx-legacy in the next commit, which is what it will infer otherwise (and makes rebasing more of a pain than it should be) 2019-06-25 01:29:49 +00:00			`*************************************`
docs: Make CMake build system default, mark GNU Make as legacy option All `-cmake` suffixes are removed Where a GNU Make option is renamed, the `-legacy` suffix is used 2019-06-25 01:26:53 +00:00			`Customized Setup of Toolchain`
docs: Functional renaming commit for CMake-as-default Rename all the files which will be edited substantially in the next commit, without changing their contents Docs will not build for this ocmmit. This is done so that git doesn't decide we renamed xxx-cmake -> xxx-legacy in the next commit, which is what it will infer otherwise (and makes rebasing more of a pain than it should be) 2019-06-25 01:29:49 +00:00			`*************************************`
Removed redundant 'Logging to Host' and docs cleaning 2017-08-25 20:35:33 +00:00
docs: Functional renaming commit for CMake-as-default Rename all the files which will be edited substantially in the next commit, without changing their contents Docs will not build for this ocmmit. This is done so that git doesn't decide we renamed xxx-cmake -> xxx-legacy in the next commit, which is what it will infer otherwise (and makes rebasing more of a pain than it should be) 2019-06-25 01:29:49 +00:00			:link_to_translation:`zh_CN:[中文]`

docs: Make CMake build system default, mark GNU Make as legacy option All `-cmake` suffixes are removed Where a GNU Make option is renamed, the `-legacy` suffix is used 2019-06-25 01:26:53 +00:00			Instead of downloading binary toolchain from Espressif website (see :ref:`get-started-set-up-tools`) you may build the toolchain yourself.
Removed redundant 'Logging to Host' and docs cleaning 2017-08-25 20:35:33 +00:00
			`If you can't think of a reason why you need to build it yourself, then probably it's better to stick with the binary version. However, here are some of the reasons why you might want to compile it from source:`

			`- if you want to customize toolchain build configuration`
			`- if you want to use a different GCC version (such as 4.8.5)`
			`- if you want to hack gcc or newlib or libstdc++`
			`- if you are curious and/or have time to spare`
			`- if you don't trust binaries downloaded from the Internet`

			`In any case, here are the instructions to compile the toolchain yourself.`

			`.. toctree::`
			`:maxdepth: 1`

			`windows-setup-scratch`
			`linux-setup-scratch`
docs: update all documents in get started section and keep line number consistent 2021-07-22 07:54:47 +00:00			`macos-setup-scratch`