linux-setup-scratch.rst 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105
  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 install git wget ncurses-devel flex bison gperf python pyserial python-pyelftools cmake ninja-build ccache
  12. - Ubuntu and Debian::
  13. sudo apt-get install git wget libncurses-dev flex bison gperf python python-pip python-setuptools python-serial python-click python-cryptography python-future python-pyparsing python-pyelftools cmake ninja-build ccache libffi-dev libssl-dev
  14. - Arch::
  15. sudo pacman -S --needed gcc git make ncurses flex bison gperf python-pyserial python-click python-cryptography python-future python-pyparsing python-pyelftools cmake ninja ccache
  16. .. note::
  17. 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".
  18. Compile the Toolchain from Source
  19. =================================
  20. - Install dependencies:
  21. - CentOS 7::
  22. sudo yum install gawk gperf grep gettext ncurses-devel python python-devel automake bison flex texinfo help2man libtool make
  23. - Ubuntu pre-16.04::
  24. sudo apt-get install gawk gperf grep gettext libncurses-dev python python-dev automake bison flex texinfo help2man libtool make
  25. - Ubuntu 16.04 or newer::
  26. sudo apt-get install gawk gperf grep gettext python python-dev automake bison flex texinfo help2man libtool libtool-bin make
  27. - Debian 9::
  28. sudo apt-get install gawk gperf grep gettext libncurses-dev python python-dev automake bison flex texinfo help2man libtool libtool-bin make
  29. - Arch::
  30. TODO
  31. Create the working directory and go into it::
  32. mkdir -p ~/esp
  33. cd ~/esp
  34. Download ``crosstool-NG`` and build it:
  35. .. include-build-file:: inc/scratch-build-code.inc
  36. .. 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.
  37. Build the toolchain::
  38. ./ct-ng xtensa-{IDF_TARGET_TOOLCHAIN_NAME}-elf
  39. ./ct-ng build
  40. chmod -R u+w builds/xtensa-{IDF_TARGET_TOOLCHAIN_NAME}-elf
  41. Toolchain will be built in ``~/esp/crosstool-NG/builds/xtensa-{IDF_TARGET_TOOLCHAIN_NAME}-elf``.
  42. Add Toolchain to PATH
  43. =====================
  44. The custom toolchain needs to be copied to a binary directory and added to the ``PATH``.
  45. Choose a directory, for example ``~/esp/xtensa-{IDF_TARGET_TOOLCHAIN_NAME}-elf/``, and copy the build output to this directory.
  46. To use it, you will need to update your ``PATH`` environment variable in ``~/.profile`` file. To make ``xtensa-{IDF_TARGET_TOOLCHAIN_NAME}-elf`` available for all terminal sessions, add the following line to your ``~/.profile`` file::
  47. export PATH="$HOME/esp/xtensa-{IDF_TARGET_TOOLCHAIN_NAME}-elf/bin:$PATH"
  48. .. note::
  49. 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``.
  50. Log off and log in back to make the ``.profile`` changes effective. Run the following command to verify if ``PATH`` is correctly set::
  51. printenv PATH
  52. You are looking for similar result containing toolchain's path at the beginning of displayed string::
  53. $ printenv PATH
  54. /home/user-name/esp/xtensa-{IDF_TARGET_TOOLCHAIN_NAME}-elf/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
  55. Instead of ``/home/user-name`` there should be a home path specific to your installation.
  56. Next Steps
  57. ==========
  58. To carry on with development environment setup, proceed to :ref:`get-started-get-esp-idf`.