linux-setup-scratch.rst 4.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111
  1. ******************************************
  2. Setup Linux Toolchain from Scratch
  3. ******************************************
  4. :link_to_translation:`zh_CN:[中文]`
  5. The following instructions are alternative to downloading binary toolchain from Espressif website. To quickly setup the binary toolchain, instead of compiling it yourself, backup and proceed to section :doc:`linux-setup`.
  6. .. note:: The reason you might need to build your own toolchain is to solve the Y2K38 problem (time_t expand to 64 bits instead of 32 bits).
  7. Install Prerequisites
  8. =====================
  9. To compile with ESP-IDF you need to get the following packages:
  10. - CentOS 7::
  11. sudo yum -y update && sudo yum install git wget ncurses-devel flex bison gperf python3 python3-pip cmake ninja-build ccache dfu-util libusbx
  12. CentOS 7 is still supported but CentOS version 8 is recommended for a better user experience.
  13. - Ubuntu and Debian::
  14. sudo apt-get install git wget libncurses-dev flex bison gperf python3 python3-pip python3-setuptools python3-serial python3-cryptography python3-future python3-pyparsing python3-pyelftools cmake ninja-build ccache libffi-dev libssl-dev dfu-util libusb-1.0-0
  15. - Arch::
  16. sudo pacman -Sy --needed gcc git make ncurses flex bison gperf python-pyserial python-cryptography python-future python-pyparsing python-pyelftools cmake ninja ccache dfu-util libusb
  17. .. note::
  18. CMake version 3.5 or newer is required for use with ESP-IDF. Older Linux distributions may require updating, enabling of a "backports" repository, or installing of a "cmake3" package rather than "cmake".
  19. Compile the Toolchain from Source
  20. =================================
  21. - Install dependencies:
  22. - CentOS 7::
  23. sudo yum install gawk gperf grep gettext ncurses-devel python3 python3-devel automake bison flex texinfo help2man libtool make
  24. - Ubuntu pre-16.04::
  25. sudo apt-get install gawk gperf grep gettext libncurses-dev python python-dev automake bison flex texinfo help2man libtool make
  26. - Ubuntu 16.04 or newer::
  27. sudo apt-get install gawk gperf grep gettext python python-dev automake bison flex texinfo help2man libtool libtool-bin make
  28. - Debian 9::
  29. sudo apt-get install gawk gperf grep gettext libncurses-dev python python-dev automake bison flex texinfo help2man libtool libtool-bin make
  30. - Arch::
  31. sudo pacman -Sy --needed python-pip
  32. Create the working directory and go into it::
  33. mkdir -p ~/esp
  34. cd ~/esp
  35. Download ``crosstool-NG`` and build it:
  36. .. include-build-file:: inc/scratch-build-code.inc
  37. .. note:: To create a toolchain with support for 64-bit time_t, you need to remove the ``--enable-newlib-long-time_t`` option from the ``crosstool-NG/samples/xtensa-esp32-elf/crosstool.config`` file in 33 and 43 lines.
  38. Build the toolchain::
  39. ./ct-ng {IDF_TARGET_TOOLCHAIN_PREFIX}
  40. ./ct-ng build
  41. chmod -R u+w builds/{IDF_TARGET_TOOLCHAIN_PREFIX}
  42. Toolchain will be built in ``~/esp/crosstool-NG/builds/{IDF_TARGET_TOOLCHAIN_PREFIX}``.
  43. Add Toolchain to PATH
  44. =====================
  45. The custom toolchain needs to be copied to a binary directory and added to the ``PATH``.
  46. Choose a directory, for example ``~/esp/{IDF_TARGET_TOOLCHAIN_PREFIX}/``, and copy the build output to this directory.
  47. To use it, you will need to update your ``PATH`` environment variable in ``~/.profile`` file. To make ``{IDF_TARGET_TOOLCHAIN_PREFIX}`` available for all terminal sessions, add the following line to your ``~/.profile`` file::
  48. export PATH="$HOME/esp/{IDF_TARGET_TOOLCHAIN_PREFIX}/bin:$PATH"
  49. .. note::
  50. If you have ``/bin/bash`` set as login shell, and both ``.bash_profile`` and ``.profile`` exist, then update ``.bash_profile`` instead. In CentOS, ``alias`` should set in ``.bashrc``.
  51. Log off and log in back to make the ``.profile`` changes effective. Run the following command to verify if ``PATH`` is correctly set::
  52. printenv PATH
  53. You are looking for similar result containing toolchain's path at the beginning of displayed string::
  54. $ printenv PATH
  55. /home/user-name/esp/{IDF_TARGET_TOOLCHAIN_PREFIX}/bin:/home/user-name/bin:/home/user-name/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
  56. Instead of ``/home/user-name`` there should be a home path specific to your installation.
  57. Python 2 deprecation
  58. ====================
  59. Python 2 reached its `end of life <https://www.python.org/doc/sunset-python-2/>`_ and support for it in ESP-IDF will be removed soon. Please install Python 3.6 or higher. Instructions for popular Linux distributions are listed above.
  60. Next Steps
  61. ==========
  62. To carry on with development environment setup, proceed to :ref:`get-started-get-esp-idf`.