User Tools

Site Tools


building_a_toolchain

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
building_a_toolchain [2016/04/21 17:04]
mimbert
building_a_toolchain [2017/01/10 23:31] (current)
onicolas
Line 28: Line 28:
 The only limitation is that this script is only supported on recent (stable or testing) linux debian 64 bits. Running it in another environment may be possible with some limitations. For example, it's quite straightforward to run it under a recent ubuntu 64 bits, a few package names will need to be adapted. On the other hand, it won't work __at all__ on a 32 bits system or under windows or macos. The only limitation is that this script is only supported on recent (stable or testing) linux debian 64 bits. Running it in another environment may be possible with some limitations. For example, it's quite straightforward to run it under a recent ubuntu 64 bits, a few package names will need to be adapted. On the other hand, it won't work __at all__ on a 32 bits system or under windows or macos.
  
-The main advantage of the [[https://​github.com/​CorteXlab/​cxlb-build-toolchain|cxlb-build-toolchain]] is that it takes care to install ​everything in a given directory, as regular user. It then generates and installs two scripts, one that has to be run by root, to configure the dynamic loader and udev to use the toolchain, the other that has to be sourced by the user which will use the toolchain, to configure the environment. Thus:+The main advantage of the [[https://​github.com/​CorteXlab/​cxlb-build-toolchain|cxlb-build-toolchain]] is that it takes care of installing ​everything in a given directory, as regular user. It then generates and installs two scripts, one that has to be run as root, to configure the dynamic loader and udev to use the toolchain, the other that has to be sourced by the user which will use the toolchain, to configure the environment. Thus:
  
 * as it runs as a regular user, there is zero risk to damage anything in the system, you are sure that anything it does is restricted to the rights of the user running the script. The only thing that has to be run as root is a single script generated at the end, which is easy to review and audit. * as it runs as a regular user, there is zero risk to damage anything in the system, you are sure that anything it does is restricted to the rights of the user running the script. The only thing that has to be run as root is a single script generated at the end, which is easy to review and audit.
-thus,you are sure that it does not conflict with anything in the regular directory tree structure of your system. In particular, it cannot ​conflit ​with the debian package system (or the package manager of your other distribution).+* you are then sure that it does not conflict with anything in the regular directory tree structure of your system. In particular, it cannot ​conflict ​with the package manager of your distribution.
 * everything from the toolchain is kept isolated in the toolchain install directory, instead of being scattered everywhere. * everything from the toolchain is kept isolated in the toolchain install directory, instead of being scattered everywhere.
-* it is possible to have more than one toolchain ​installed in parallel. You only need to re-run the root script to switch to a different toolchain, and reboot (or possibly only restart udev? that needs to be checked), and re-source the environment configuration script.+* it is possible to have several toolchains ​installed in parallel. You only need to re-run the root script to switch to a different toolchain, and reboot (or possibly only restart udev? that needs to be checked), and re-source the environment configuration script.
  
 When building a toolchain on a user's workstation,​ the user is not forced to build everything. For example, a user willing to experiment only with usrp can avoid installing all picosdr stuff (xilinx ise, digilent hs2 jtag, adp). When building a toolchain on a user's workstation,​ the user is not forced to build everything. For example, a user willing to experiment only with usrp can avoid installing all picosdr stuff (xilinx ise, digilent hs2 jtag, adp).
building_a_toolchain.txt ยท Last modified: 2017/01/10 23:31 by onicolas