62ed221daf
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)
28 lines
1,007 B
ReStructuredText
28 lines
1,007 B
ReStructuredText
.. _get-started-customized-setup-cmake:
|
|
|
|
*************************************
|
|
Customized Setup of Toolchain (CMake)
|
|
*************************************
|
|
|
|
:link_to_translation:`zh_CN:[中文]`
|
|
|
|
Instead of downloading binary toolchain from Espressif website (see :ref:`get-started-set-up-tools-cmake`) 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
|
|
|